5 ms·
I dislike shitty languages and successfully avoid using them myself, but I do have to be a bit happy with NPM ecosystem teaching people to reuse more code.
by Ericson2314 10y ago
I dislike shitty languages and successfully avoid using them myself, but I do have to be a bit happy with NPM ecosystem teaching people to reuse more code.
- overcast 10y agoWhile there is no arguing the pitfalls of dealing with Javascript. As a one man team, to build a product with the same language on the backend, that I've already been using on the front end. Is awesome. The ability to fire up a Node.js project on a server is even easier than a PHP one, which is arguably why PHP took off in the first place. And like you mentioned, I think the NPM system is awesome, super easy to use, and a voracious community. Sure there is TONS of not nice things about JS, but it's slowly evolving to be better(ES6 + Promises), and it's not going anywhere anytime soon.
- bigtunacan 10y agoThe only way to avoid using shitty languages would be to stop programming altogether. I have found in my experience a pattern that repeats itself. 1) I find a language (B) that I think is great because it solves X problem with the language (A) previously being used. 2) I use that new language long enough that eventually I learn it's pitfalls and hate it. 3) Switch to language (C) because it fixes problems found in language (B). Eventually this loops.
- Ericson2314 10y agoI'm sorry that's been your experience. I've been using Haskell for 4 years, Rust for 2, happy with both. Anything I don't like other people usually don't like and is fixable.
- andrewprock 10y agoFor years I was stuck in a cycle: A->B->A->B ... Where A was C++, and B was Python.
- PeCaN 10y agoThere are less shitty languages. I'd consider mine to be OCaml and Perl (and Rust is growing on me, but I might be in the first phase above). I think, ultimately, this just boils down to “know a lot of tools and use the right tool for the job”.
- int_19h 10y agoI find that it doesn't loop for me, unless you count new versions of old languages (which fix old problems) same as old. The sequence is familiar, but in general, I find the tools that I use today better, in very specific ways, than tools that I've been using 5 years ago, which were better than those from 10 years ago etc. So it's more of a spiral. A straight line would be better, but I'll take progress in whatever form.
- wvenable 10y agoI think NPM has finally shown that you can, in fact, have too much code reuse. The representative example for me is this actual isPositiveInteger module: var passAll = require('101/pass-all') var isPositive = require('is-positive') var isInteger = require('is-integer') module.exports = passAll(isPositive, isInteger) You don't even want to know what the is-positive and is-integer modules look like. Software pundits have been saying how modern programming is just wiring together existing components for years; the node ecosystem has taken that to its illogical extreme.
- maxxxxx 10y agoIs this real or are you kidding?
- DannyBee 10y agoReal. However, the same day the left-pad debacle stuff was on HN, this was changed to be self-contained: https://github.com/tjmehta/is-positive-integer/commits/master/index.js https://github.com/tjmehta/is-positive-integer/commits/maste...
- dsp1234 10y agoYour information is out of date. https://github.com/tjmehta/is-positive-integer/blob/master/index.js https://github.com/tjmehta/is-positive-integer/blob/master/i...
- userbinator 10y agoNo discussion on Node.js and "overmodularisation" is complete without a mention of the left-pad debacle: https://news.ycombinator.com/item?id=11348798 https://news.ycombinator.com/item?id=11348798
- prodigal_erik 10y agoNo matter how few dependencies you have, any of them can break you if your build system automatically moves you to an updated version without first testing it.