3 ms·
I don't get it. Does array-last* has any sense? If someone needs to include a package for last() so the code is more bugproof and stable, I don't know what to e
by feiss 10y ago
I don't get it. Does array-last* has any sense? If someone needs to include a package for last() so the code is more bugproof and stable, I don't know what to expect in more complex algorithms..
This, like many stuff I see in the javascript world, is overegineering.
* https://github.com/angus-c/just/blob/master/packages/array-last/index.js https://github.com/angus-c/just/blob/master/packages/array-l...
- nojvek 10y agoCan't put the blame of one bad package on the whole community. If there is a bad package don't use it. I've seen lots of well engineered packages with zero dependencies. E.g typescript. Entire compiler and language server. No dependencies. Es6 is a decent library out of the box. I always only add a dependent if it's something not trivial. A lot of the shitty packages came out before tree shaking was a thing. There is an argument. Should you just have a large hash table of functions that you reference. Those in the bandwagon go for the one function packages.