4 ms·
I've been programming since the late 90s and as recently as one or two years ago I would have agreed with a lot of this. However, having recently come back to J
by corford 6y ago
I've been programming since the late 90s and as recently as one or two years ago I would have agreed with a lot of this. However, having recently come back to JS and currently in the midst of developing a large, complex non-frontend app in it; I have to say the language, tooling, standards and ecosystem have jumped forward significantly.
It has honestly been a pleasure building this out. Yes, you still need to be selective about dependencies but that's the case for many languages. Beyond that, JS/Node in 2020 (in the right hands and for the right project) is pretty awesome.
- dijit 6y agoThe parent is not decrying developing things right now. They are suggesting that what is built will not survive a very long time. It would be more interesting if you had picked up a 3yr old project and could tell us your experience with that; failing this it would only be interesting if you come back in a few years to tell us how it is.
- corford 6y ago>They are suggesting that what is built will not survive a very long time. I suspect that thanks to the recent jumps forward (language itself, common best practices, tooling) that this argument doesn't hold as much weight as it once did. I see a lot of JS library code today that looks eminently supportable and survivable beyond a ~3yr time horizon.
- dijit 6y agoI would like to agree, but given that we have no evidence for this and a history that has not supported this assertion- we cannot make that claim. Only time will tell.
- cmrdporcupine 6y agoHonestly what the post author is describing sounds about my experience with the Java + Maven deps world about 10 years ago when I last used it. A giant trail of dependencies of questionable quality (and how many problems with commons-logging?). I have no desire to write JS, really, but it doesn't sound unfamiliar.