3 ms·
"In most web applications the "bottle-neck" is going to be DOM interaction. It is very unlikely that you will notice a performance hit at all." uhhh, 2 wrongs
by ceedan 12y ago
"In most web applications the "bottle-neck" is going to be DOM interaction. It is very unlikely that you will notice a performance hit at all."
uhhh, 2 wrongs don't make it right?
"It is very unlikely that you will notice a performance hit at all."
Until you do..
--
I could never justify using this stuff at work. It's inefficient, unfamiliar to most JS developers and even if it did pass a peer review, nobody else would actually want to maintain it.
- chriswarbo 12y ago> I could never justify using this stuff at work. It's ... unfamiliar to most JS developers and even if it did pass a peer review, nobody else would actually want to maintain it. The same could be said for any API. Currying is actually very unobtrusive; the only time a curried function behaves differently to its uncurried counterpart is when it's given a 'wrong' number of arguments. The benefit is never having to perform manual eta-expansion (ie. any time we write a redundant wrapper like "function(x) { return bar(a, b, c, x); }"). As for efficiency, I default to having the machines doing things to save developer's time and only do things the other way around when it's untenable (or for fun).