JSX: yes
TypeScript: sure
CommonJS & ESM: no problem
Decorators: yeehaw
Web Components: how dare you, this is too much tooling overhead and complexity
@zachleat think of their poor compilers 😏

@zachleat

Any current tool for JS development is bound to be replaced by a web standard sooner or later. In fact, CommonJS is already obsolete.

The main reason React and friends are still relevant is because Web Components are still incomplete.

@jgg I dunno if I’d say CommonJS is obsolete quiet yet—definitely still has a place in Node.js land (at least until CJS/ESM compat ships)

@zachleat

True, Node.js has a legacy issue there. Let's hope they solve it soon; it would make much easier to package libraries for use on Node.js and transpilation free web apps.

It is amazing how liberating can be to make a mid size web app without transpilation after years of suffering the Node cruft.

@zachleat A few things I learned over years:

- Angular 9 -> Angular 11 (4 weeks)
- Angular 11 -> Angular 14 (3 months)
- Angular 14 -> Angular 16 (2 weeks)
- Vue 2 -> Vue 3 (4 months and still counting)
- Web components (casting amused glances at the above migrations since day 1, years ago, no migrations required till date)

Web components just make life easier for long haul.

@naiyer whew, I’ve definitely felt that Vue 2/3 pain
@zachleat CSS: what do I look like a fucking rocket scientist? WTF even is this shit?
@peruvianidol 🫣🫣🫣 I still have trouble wrapping my head around a preference for HTML over CSS, it just doesn’t fit the stereotype 😅