4 ms·
Yeah. I've just taken to ignoring those responses. As far as I'm concerned, jQuery & lodash are part of the "standard library". Certainly there are cases where
by warbiscuit 10y ago
Yeah. I've just taken to ignoring those responses.
As far as I'm concerned, jQuery & lodash are part of the "standard library". Certainly there are cases where one or the other isn't needed for a particularly application. But if you're doing anything with the DOM, or doing anything more complex than simple if/then callbacks, you're either using them or you're reimplementing them bit by bit.
Certainly jquery has some... warts... but I haven't seen any project emerge that's succeeded at being a cleaned up replacement. And jquery 3.0 looks like it's trying to forge ahead in that direction itself.
(Still hate jquery's inconsistent ajax callback signatures. sigh.)
- Roboprog 10y agoI have been using Ramdajs, rather than lodash, but they both do about the same thing. One difference is that Ramda puts the functions before the data in its library calls, so that you can curry/apply the app logic function (e.g. - perhaps for a map or filter), save the resulting function and use it elsewhere. Lodash looks nice, though, in that its partial function application mechanisms seem a bit more flexible than curry (only) - e.g. - I want to make a function with 0-arity, and bind it to an event handler, which Ramda won't do.
- lloyd-christmas 10y agolodash has that ability from a sub-module "lodash/fp": https://github.com/lodash/lodash/wiki/FP-Guide https://github.com/lodash/lodash/wiki/FP-Guide
- Roboprog 10y agoThanks. I wonder if somebody has a good comparison of the Lodash vs Ramda written up. Probably, but I haven't done the google and evaluation yet :-(