If you had years of experience in a wide array of technologies and languages, you'd be aware of that which is, and has been, obvious to the rest of us for the past 2-3 decades.
If you had years of experience in a wide array of technologies and languages, you'd be aware of that which is, and has been, obvious to the rest of us for the past 2-3 decades.
Nothing about function length determines utility. There are many one lines that match many people's needs repeatedly.
> When you have 100 such modules which don't quite work
This is worrying. How are you picking the modules you use? 100x popular modules from npm - with git repos, unit tests, READMEs, and hundreds of other users - beat 100x functions implemented in-house for NIH (or more likely, 100x functions copy pasted from Stack Overflow).
> If you had years of experience in a wide array of technologies and languages
Please don't assume things about other people. It's very rude, and it makes you look bad when you're wrong.
At least there are JS programmers that seem aware of it and agree that this has to change. So there's still hope I guess.
I completely agree. I still can't understand why the language that we depend on for increasingly large-scale front-end work still works like this:
[1, 10, 2, 21].sort() // returns: [1, 10, 2, 21]
It's 2016, software engineering is purported to be a profession, and we still have the worst tools imaginable.
.sort(sorts.numerical)
Using npms 'sorts' module