4 ms·
I wasn't entirely serious. There is just a lot of churn in the library/framework space for JS. There are constantly people trying to invent "like X but better"
by jannes 8y ago
I wasn't entirely serious.
There is just a lot of churn in the library/framework space for JS. There are constantly people trying to invent "like X but better", where X can be absolutely anything in your JS workflow.
If you don't use npm and only rely on the builtin node APIs this would not apply to you as much, though.
On top of that there are always new language features being introduced to EcmaScript and implemented in V8. This means that if you're not using those latest features, some might say your code is outdated.
- scandox 8y agoYeah sorry sense of humour failure on my part
- fenomas 8y ago> There are constantly people trying to invent "like X but better", where X can be absolutely anything in your JS workflow. Complaints like this always mystify me. Would things be better if what you describe wasn't the case?
- adrianhel 8y agoThere was a lot of churn in JS. Things have gotten pretty damn stable. I usually use Express(2010), Socket.io(2014) and React(2013) for new projects. The libraries that break with new versions are the ones that rely on exotic features.