Which Is Why I Use Part
I like reading my newsletters. A weekly summary like JS weekly allows me to see if my twitter or github network was on top of the same hot news as the publisher. The more I click in and read, the worse I’ve done staying on top of things.
- First, we’re just using native methods with a different, predictable signature.
- Second, nothing is done for you.
Part isn’t a library and isn’t trying to be one. It is trying to allow flexibility with common, well-understood methods and encourage a functional approach.
My guess: this doesn’t perform as well as a library version or possibly even Paul’s, native version. However, performance isn’t
always what you need. Sometimes, you need readable syntax and the freedom to move along to the next problem. If performance is
your problem, you should be able to replace the
invokeAll function with one that does exactly the same thing using
for loop but keep your useage nice and readable. Remember, be kind to your future self.