4 ms·

Yeah, articles that proclaim the end of frameworks due to Web Components always revolve around a misunderstanding of what those frameworks bring. This article,

by Vinnl 8y ago

Yeah, articles that proclaim the end of frameworks due to Web Components always revolve around a misunderstanding of what those frameworks bring. This article, likewise, starts out on the same incorrect premise: > [Frameworks like Angular and React] have enabled us to do what we always wanted but never were able to: creating reusable autonomous frontend components That's not what we always wanted to do, and not why people are using these frameworks. How often do you re-use your Angular and React application?

supermatt 8y ago
I reuse react components ALL the time. I think the problem with the article is that it is just looking at components (as a developer I have wanted the encapsulation this methodology brings), whereas react offers more than that - the virtual DOM, for example.
- Vinnl 8y ago
  Ah, yes - within the same applications, components are often re-used. Still, it's a stretch to say code re-use is the main reason people are using React. Rather, its advantage lies in its composability and how easy it makes it to separate view logic from other logic. And probably a few other reasons that other people would name as well; in any case, it's not just the ability to re-use components, and an alternative only providing that part is not going to replace React in my applications any time soon.
  - supermatt 8y ago
    I reuse components in different applications. There are also popular third-party components (and even whole libraries) to be found on github and elsewhere. I don't think web components will replace react, simply because they do different things. You can write web components in react which gives you the best of both worlds.
pjmlp 8y ago
> How often do you re-use your Angular and React application? A lot, our Angular components are re-usable across projects.
jsight 8y ago
Our company standardized on React company-wide along with a company-built framework of reusable components to share across all applications. Apparently at least some people choose frameworks because they want that.
newman8r 8y ago
I'm constantly reusing modules/components/pipes/guards/interceptors/etc across angular projects. Saves a lot of time. It's not the reason I use the framework, but it gives me more incentive to stick with it.

by Vinnl 8y ago

supermatt 8y ago

I reuse react components ALL the time. I think the problem with the article is that it is just looking at components (as a developer I have wanted the encapsulation this methodology brings), whereas react offers more than that - the virtual DOM, for example.

Vinnl 8y ago
Ah, yes - within the same applications, components are often re-used. Still, it's a stretch to say code re-use is the main reason people are using React. Rather, its advantage lies in its composability and how easy it makes it to separate view logic from other logic. And probably a few other reasons that other people would name as well; in any case, it's not just the ability to re-use components, and an alternative only providing that part is not going to replace React in my applications any time soon.
- supermatt 8y ago
  I reuse components in different applications. There are also popular third-party components (and even whole libraries) to be found on github and elsewhere. I don't think web components will replace react, simply because they do different things. You can write web components in react which gives you the best of both worlds.

pjmlp 8y ago

> How often do you re-use your Angular and React application? A lot, our Angular components are re-usable across projects.

jsight 8y ago

Our company standardized on React company-wide along with a company-built framework of reusable components to share across all applications. Apparently at least some people choose frameworks because they want that.

newman8r 8y ago

I'm constantly reusing modules/components/pipes/guards/interceptors/etc across angular projects. Saves a lot of time. It's not the reason I use the framework, but it gives me more incentive to stick with it.