3 ms·
They didn't break compatibility. NodeJS never attempted to be compatible with the Web. The design work that TC-39 and the browser makers did is also much bett
by pwdisswordfish6 6y ago
They didn't break compatibility. NodeJS never attempted to be compatible with the Web. The design work that TC-39 and the browser makers did is also much better than what the NodeJS community puts out. And it's a design that was in ECMAScript 6. Six years later, and you still have to opt in. The TypeScript team got it right, working in a way that NodeJS should have been taken lessons from.
- Scarbutt 6y agoThe design work that TC-39 and the browser makers did is also much better than what the NodeJS community puts out Like the dumb broken Maps and Sets?
- jiofih 6y agoYeah, technically better, at the cost of huge complexity. CommonJS was easy to implement anywhere and dead simple. We only need static analyzers and tree-shaking optimizations because the JS ecosystem went wild on dependencies. I honestly think we were better off 10 years ago. > NodeJS never attempted to be compatible with the Web It goes the other way around? Node caved in and support modules now, what has been done in tc-39 for web modules to be compatible with node (considering it predates all of it)? There is no “JS community vs Node community” btw.