Reply to post:

Languishing lodash library loophole finally fitted for a fix: It's only taken since October to address security bug

Kubla Cant

Most people probably use Lodash to try to reduce the uncertainties of writing JavaScript*.

As pointed out here you can do without Lodash. But in many cases the native ES5/ES6 code is more verbose or less transparent than the Lodash alternative. Your therefore have the choice of inlining the native code everywhere, which lays up technical debt for the inevitable day when a defect is discovered in it, or writing your own library, which is really just dogfooding Lodash.

* Probably because I'm an old fart who learned coding on less high-spirited languages, I find JavaScript a constant source of anxiety, even though I spend a lot of time on it these days. It's bizarre they way it puts Tony Hoare's billion-dollar mistake in the shade by having three kinds of nullity, even though it only has about half a dozen datatypes that are constantly turning into each other.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon