HN Explorer

Ask HN: Anybody still into ES5 + traditional Javascript dev workflow? Why?

3 points by lewisjoe ↗ HN
Client Javascript development has drastically changed in the last 5-7 years. ES6+ Standards, module bundlers, Managing dependencies with NPM, Typescript & such modern elements in the toolchain is becoming the de-facto.

Are there any companies, projects/products, indie devs out there still sticking to plain old JS development without the modern tools?

Are there any reasons to not switch to the modern workflow?

2 comments

[ 1.8 ms ] story [ 12.7 ms ] thread
avoidwork
i've avoided it entirely with my latest work project; no transpile, or unneeded tools... just awk & eslint.

there are no* "de-facto standards", just people doing what they think is popular 'cause they read about it on the net.