upvote

points

by wsatb10 hours ago |
comments
upvoteby austin-cheney10 hours ago|
next
[-]
Its not a conspiracy. It is just group behavior following a trend as loudly as possible.
reply
upvoteby wsatb8 hours ago|
parent|
[-]
Web components are a trend? I've been using them for close to 10 years and they're still not anywhere close to mainstream. Loudly as possible? They've quietly just kind of been there for years.

I think we have a generation of developers that only know React and they're so engrained with it they simply cannot imagine a world without it. If you really can't find a use case for web components then you're living in a bubble.

reply
upvoteby austin-cheney8 hours ago|
parent|
next
[-]
We have been through all this before with jQuery. The generation of JavaScript developers at the beginning on React only knew jQuery and they really wanted to shoehorn all the jQuery nonsense into the standards. From their perspective it makes complete sense because that is the only one way to do things. They got querySelectors into the DOM.

Now we are seeing the exact same thing again. People only know React, so they want the standards to look like the only one thing they know. That doesn't make it a good idea. Every time this comes up we exchange simplicity and performance for easiness and temporary emotional comfort. Its only a temporary win until the next generational trend comes along.

reply
upvoteby troupo6 hours ago|
parent|
prev|
[-]
> If you really can't find a use case for web components then you're living in a bubble.

There's a very tiny use-case for web components. And even there it's riddled with a huge amount of potential (and actual) footguns that "in the bubble" devs have been talking about for a decade at this point, and some which were finally acknowledged: https://w3c.github.io/webcomponents-cg/2022.html (no updates since)

reply
upvoteby wsatb3 hours ago|
parent|
[-]
> There's a very tiny use-case for web components.

That's weird, we've been using them at my company for a number of years and there's plenty of other examples of them being adopted elsewhere too. This continues to read as, "it's not React, so it's bad."

reply
upvoteby troupo6 hours ago|
prev|
[-]
> Who are "they"? You sound like you think there's some giant conspiracy against JS frameworks.

Yes. There is. The main developers and proselityzers were completely insanely biased against web frameworks (especially React).

It wasn't even a conspiracy. All you had to do was to follow Alex Russel (the person who introduced the idea of web components in the first place) and see his interactions with framework authors and his views towards web frameworks.

The new people in the space driving the specs are hardly any better. E.g. their reactions to Ryan Carniato's rather mild criticism of Web Components is just filled with vile, bile, and hate.

They literally refuse to even admit they have a problem, or want to look at any other solutions than the ones they cook up.

> but a browser feature is kind of what it is. It can take years for features to make it into enough browsers to make them usable.

Strange, browsers push dozens of specs for web components without ever taking any time to see if the yet another half-baked "solution" is actually workable.

reply
upvoteby wk_end4 hours ago|
parent|
[-]
Some links to examples of the sort of behaviour you're describing would be really helpful here (I say this as someone who is sympathetic - I work with on a web component/Lit codebase in my 9-5 and I'm not a fan, compared to the React workflow I had in a past life).
reply