Comment by andrewmcwatters

Comment by andrewmcwatters 7 hours ago

I moved my entire business off React and now I don’t have to worry about tinkerers at Meta deciding to reinvent React every 2 years and tricking everyone by keeping the name again and again.

Web components are fantastic. They are the real future.

rhet0rica 3 hours ago

https://i.imgur.com/7ITZb7d.jpeg

Aren't web components a pain in the ass to use?

Reply View 4 replies

prisenco 38 minutes ago

They could be better, but they're not nearly as difficult as people like to make them out to be.
And they come with extra benefits like no build tool required and native browser support.

Reply View | 0 replies
bythreads 3 hours ago

Nope
Lit.dev

Reply View | 2 replies
- brenainn 3 hours ago
  
  I like lit. I'm not primarily a web developer and I've found it intuitive and easy to read and write. What I find more confusing than frameworks is building, bundling, ES modules, the whole NPM ecosystem.
  
  Reply View | 1 reply
  
  balamatom 3 minutes ago
  
  >building, bundling, ES modules, the whole NPM ecosystem.
  That's evolved hand in hand with the React monoculture over the past 10-15 years by way of a project called Babel. Which set out to provide progressive enhancement for the original ES5 to ES6 migration, and then in classic POSIWID fashion began to thrive on a suite of a la carte incompatibilities.
  So yeah, plenty of things in JS infra that look like they've been designed to be a pain in the ass, probably as a result of more inept moat-building in the then-newly ballooning field of frontend dev. Readers might look up whan an import map is sometime, as well as where it is and isn't supported.
  
  Reply View | 0 replies

echelon 2 hours ago

React gets reinvented every year?

Are you talking about functional components instead of class components? What big changes am I missing here? It seems pretty static to me.

Reply View 0 replies