3 ms·

I don't feel it's fair to brand "web components" as a technology that was in direct competition with React. I think the nuance matters. They may have been solv

I don't feel it's fair to brand "web components" as a technology that was in direct competition with React. I think the nuance matters. They may have been solving similar problems then, and they may be optimized for different things now. But Web components are a web standard, and React is not. Pushing for web standard technologies is inherently unbiased because that's just betting on the platform. This results in pushing for platform improvements (like declarative shadow dom so it plays well with SSR, etc), and then everyone benefits. IMO it'd only be a bias take if web components were branded as having no issues whatsoever, or that they are the most optimal solution for everything. I think it's okay to say, "web components currently don't solve my problems and that's why I'm looking to use something else like React or Solid". However, I've not seen this sentiment shared when it's the other way around with React. It's always "no one got fired for picking React" instead of actually evaluating what will deliver the most value to your users.

pcthrowaway 3y ago
> Pushing for web standard technologies is inherently unbiased because that's just betting on the platform. There's a ton of politics around web standards, and you can bet if Google manages to push through Web Environment Integrity, I will not consider people suggesting to use it "unbiased because it's a standard"
- hasanhaja 3y ago
  That's a fair point. I didn't consider that
dahwolf 3y ago
I'd take that point further and state that React is in no competition with anything. React was invented because Facebook had very interactive/stateful UI as well as large teams of developers working on the same codebase. The then conventional jQuery soup approach didn't cut it. Should the web platform come up with a standards-based approach to solve the same problem, then this is not "competition", it is a blessing. It's not like React earns Facebook any revenue. Ideally, it wouldn't be needed or exist at all.
batmansmk 3y ago
React has more implementation of its components model (preact, react, solidjs, inferno,…) than web components (chrome, ff partially and safari partially), is more used and is more indépendant from the current web monopoly. Anything w3c is now a standard to keep dominance.
troupo 3y ago
> I don't feel it's fair to brand "web components" as a technology that was in direct competition with React. I think the nuance matters. Nuance doesn't matter to most proponents of web components. When they were introduced, for the first few years they were explicitly marketed as platform-native solution that makes frameworks obsolete. Now the rhetoric seems more nuanced, but it's the same. It's only been upgraded to "build with lit". > IMO it'd only be a bias take if web components were branded as having no issues whatsoever, or that they are the most optimal solution for everything Mostly they are billed like that. And any voices criticizing them are either ignored or blocked.

pcthrowaway 3y ago

> Pushing for web standard technologies is inherently unbiased because that's just betting on the platform. There's a ton of politics around web standards, and you can bet if Google manages to push through Web Environment Integrity, I will not consider people suggesting to use it "unbiased because it's a standard"

hasanhaja 3y ago
That's a fair point. I didn't consider that

dahwolf 3y ago

I'd take that point further and state that React is in no competition with anything. React was invented because Facebook had very interactive/stateful UI as well as large teams of developers working on the same codebase. The then conventional jQuery soup approach didn't cut it. Should the web platform come up with a standards-based approach to solve the same problem, then this is not "competition", it is a blessing. It's not like React earns Facebook any revenue. Ideally, it wouldn't be needed or exist at all.

batmansmk 3y ago

React has more implementation of its components model (preact, react, solidjs, inferno,…) than web components (chrome, ff partially and safari partially), is more used and is more indépendant from the current web monopoly. Anything w3c is now a standard to keep dominance.

troupo 3y ago

> I don't feel it's fair to brand "web components" as a technology that was in direct competition with React. I think the nuance matters. Nuance doesn't matter to most proponents of web components. When they were introduced, for the first few years they were explicitly marketed as platform-native solution that makes frameworks obsolete. Now the rhetoric seems more nuanced, but it's the same. It's only been upgraded to "build with lit". > IMO it'd only be a bias take if web components were branded as having no issues whatsoever, or that they are the most optimal solution for everything Mostly they are billed like that. And any voices criticizing them are either ignored or blocked.