3 ms·
It's python 2 to python 3 transition all over again, only this time it's in javascript. Which is most of what the complaints in that gist are — i.e. how much th
by azangru 3y ago
It's python 2 to python 3 transition all over again, only this time it's in javascript. Which is most of what the complaints in that gist are — i.e. how much the transitional state that we are in currently sucks.
The rest of his complaints are about how `import`s are static, whereas dynamic `import()`s are async; and he doesn't like that. To which I say, "meh".
- bhouston 3y agoOh my god have I paid my dues in this transition. I have lost days of developer time trying to support tooling that compiles into both ES Modules and CommonJS while also supporting TypeScript and tree shaking and what not. It brutally complex and the testing surface area is large with all the possible combinations.
- senko 3y ago> It's python 2 to python 3 transition all over again, only this time it's in javascript. That's not fair. Python's 2-to-3 transition is JavaScript's every other Wednesday. (yes that's a hyperbole, but the churn in the JS ecosystem really is enormous compared to any other programming language).
- azangru 3y agoAt the framework level, maybe (but then, it's userland, anything can happen there). At the fundamental level of the language itself, I don't think so.
- davidjfelix 3y agoI don't think it's hyperbole -- I think the changes are often as large and collectively more significant than 2-to-3, but the ecosystem is better at change. Even with that there are clearly factions and currents in different directions, but things generally work.