On: Web components will outlive JavaScript frameworks

[ng12]

Why do people keep hiring front-end specialists, in that case?

[pier25 → ng12]

Because front end specialists only think about the front end.

The tide is slowly turning though with Next, SvelteKit, Remix, etc. But still these frameworks are basically just rendering HTML and going full on fat client which is overkill for 80% of interactivity in web app but adds a lot of unnecessary complexity.

[dboreham → ng12]

Because a) they're available and b) people think it's a black art.

[evilduck → dboreham]

c) backend devs often proudly hold contempt for front end work and do the job poorly

[esafak → evilduck]

They don't want to get involved with tech that goes out of date every year.

[mikebelanger → esafak]

As a primarily frontend-developer, I can attest to this sentiment. I should add that most backend devs I know understand the basics of HTML, CSS and Javascript, but they're less interested in learning new framework/library/template system constantly. I have to admit, I share that attitude.

It's funny how webcomponents alone are touted as an "alternative" to a framework, despite only being one component (no pun intended) of something that solves the problem of UI state-synchronization on the browser. A better comparison would be comparing a combination of custom elements, server-side rendered HTML, and proxy objects to some SSR framework like NextJS, Remix, etc.

[evilduck → esafak]

I love that trope honestly. It's a great way to discover bad developers without having to test them first.