5 ms·

IMO they are complimentary to react. Frameworks like react/angular/backbone/vue solve the problem of creating a single page application with a nice architectur

by asurty 4y ago

IMO they are complimentary to react. Frameworks like react/angular/backbone/vue solve the problem of creating a single page application with a nice architecture and sharing code between components within the SPA. Web components solve the problem of sharing code between any application. There are opportunities to share code (eg/ data binding) and I believe that is the case (they use the same underlying browser APIs where available)

pjmlp 4y ago
With exception of React, all those frameworks have options to generate WebComponents for their component model.
- asurty 4y ago
  That is cool, didn't realize that! I wonder why React lags behind ( ? )
  - pjmlp 4y ago
    I think it is a culture issue, as far as I understand the underlying issue, the React community is not so impressed with having to deal with Web Components.
    - dmitriid 4y ago
      Realistically, there's almost no community that is impressed with having to deal with Web Components. In this discussion I keep reiterating: there are multiple reasons why none of the major frameworks and very few of the new frameworks have WCs as their foundation. At best they can consume/embed them and perhaps compile to them. And even that is rife with problems.
      - pjmlp 4y ago
        If we ignore the fact that everyone else supports them, regardless if they are their foundation or not. https://custom-elements-everywhere.com/ https://custom-elements-everywhere.com/
        dmitriid 4y ago
        > everyone else supports them That's what I said: At best they can consume/embed them and perhaps compile to them. > regardless if they are their foundation or not. And the fact that they are not forming the foundation of these frameworks should be examined and fixed, not ignnored. However, wc proponents ignore this entirely.
        pjmlp 4y ago
        Maybe because those frameworks don't want to be rewritten from scratch? It is like asking why so many graphics engines get written, instead of using raw OpenGL/Vulkan calls and extension spaghetti all over the place.
        dmitriid 4y ago
        > Maybe because those frameworks don't want to be rewritten from scratch? The absolute vast majority of new frameworks don't use web components as the foundation. Perhaps instead of burying their heads in the sand people pushing web components would should finally start asking why?
        pjmlp 4y ago
        Usually I use https://angular.io/guide/elements https://angular.io/guide/elements, https://vuejs.org/guide/extras/web-components.html#using-custom-elements-in-vue https://vuejs.org/guide/extras/web-components.html#using-cus... or https://lit.dev/ https://lit.dev/ I only need to ask why, when I have to deal with React based stuff.
        dmitriid 4y ago
      - asurty 4y ago
        Web components seem like a good idea to me. I would imagine there are a lot of libraries out there (eg/ calendars, styling frameworks) that would benefit from reuse across applications. The browser could cache it even if served from a different CDN. I'm curious what the problems are with web components that you see? Is it specifically related to how they might be used (or useless) in the major frameworks?
        dmitriid 4y ago
        > I'm curious what the problems are with web components that you see? Bitesized explanation from Rich Harris, the author of Svelte: https://twitter.com/Rich_Harris/status/1198332398561353728 https://twitter.com/Rich_Harris/status/1198332398561353728 It's from 2019, but all the issues are still there. When/If they are going to be solved, it will be by increasingly complex standards that require more and more Javascript for them to just barely function (like they couldn't even participate in form events without additional Javascript). See also a larger discussion by the author of Solid: https://youtu.be/BEWkLXU1Wlc?t=5837 https://youtu.be/BEWkLXU1Wlc?t=5837 (if the link doesn't open at the timestamp, skip to "Failed Promise of Web Components" at 1:37:17). It's a bit rambling because it was unrehearsed and on stream, but still good. He also shows and discusses other articles like Rich Harris' https://dev.to/richharris/why-i-don-t-use-web-components-2cia https://dev.to/richharris/why-i-don-t-use-web-components-2ci... and his own https://dev.to/ryansolid/maybe-web-components-are-not-the-future-hfh https://dev.to/ryansolid/maybe-web-components-are-not-the-fu... You can read them directly, but Ryan gives excellent additional context.
        asurty 4y ago
        Thanks for taking the time to find/share these links! Very informative. It sounds to me like most of the criticism's outlined are solvable. Perhaps the people behind the standard should be engaging the framework community more. I wonder if you think web components (and the problem they set out to solve) is wrong from a fundamental/architectural standpoint?

by asurty 4y ago

pjmlp 4y ago

With exception of React, all those frameworks have options to generate WebComponents for their component model.

asurty 4y ago
That is cool, didn't realize that! I wonder why React lags behind ( ? )
- pjmlp 4y ago
  I think it is a culture issue, as far as I understand the underlying issue, the React community is not so impressed with having to deal with Web Components.
  - dmitriid 4y ago
    Realistically, there's almost no community that is impressed with having to deal with Web Components. In this discussion I keep reiterating: there are multiple reasons why none of the major frameworks and very few of the new frameworks have WCs as their foundation. At best they can consume/embed them and perhaps compile to them. And even that is rife with problems.
    - pjmlp 4y ago
      If we ignore the fact that everyone else supports them, regardless if they are their foundation or not. https://custom-elements-everywhere.com/ https://custom-elements-everywhere.com/
      - dmitriid 4y ago
        > everyone else supports them That's what I said: At best they can consume/embed them and perhaps compile to them. > regardless if they are their foundation or not. And the fact that they are not forming the foundation of these frameworks should be examined and fixed, not ignnored. However, wc proponents ignore this entirely.
        pjmlp 4y ago
        Maybe because those frameworks don't want to be rewritten from scratch? It is like asking why so many graphics engines get written, instead of using raw OpenGL/Vulkan calls and extension spaghetti all over the place.
        dmitriid 4y ago
        > Maybe because those frameworks don't want to be rewritten from scratch? The absolute vast majority of new frameworks don't use web components as the foundation. Perhaps instead of burying their heads in the sand people pushing web components would should finally start asking why?
        pjmlp 4y ago
        Usually I use https://angular.io/guide/elements https://angular.io/guide/elements, https://vuejs.org/guide/extras/web-components.html#using-custom-elements-in-vue https://vuejs.org/guide/extras/web-components.html#using-cus... or https://lit.dev/ https://lit.dev/ I only need to ask why, when I have to deal with React based stuff.
        dmitriid 4y ago
    - asurty 4y ago
      Web components seem like a good idea to me. I would imagine there are a lot of libraries out there (eg/ calendars, styling frameworks) that would benefit from reuse across applications. The browser could cache it even if served from a different CDN. I'm curious what the problems are with web components that you see? Is it specifically related to how they might be used (or useless) in the major frameworks?
      - dmitriid 4y ago
        > I'm curious what the problems are with web components that you see? Bitesized explanation from Rich Harris, the author of Svelte: https://twitter.com/Rich_Harris/status/1198332398561353728 https://twitter.com/Rich_Harris/status/1198332398561353728 It's from 2019, but all the issues are still there. When/If they are going to be solved, it will be by increasingly complex standards that require more and more Javascript for them to just barely function (like they couldn't even participate in form events without additional Javascript). See also a larger discussion by the author of Solid: https://youtu.be/BEWkLXU1Wlc?t=5837 https://youtu.be/BEWkLXU1Wlc?t=5837 (if the link doesn't open at the timestamp, skip to "Failed Promise of Web Components" at 1:37:17). It's a bit rambling because it was unrehearsed and on stream, but still good. He also shows and discusses other articles like Rich Harris' https://dev.to/richharris/why-i-don-t-use-web-components-2cia https://dev.to/richharris/why-i-don-t-use-web-components-2ci... and his own https://dev.to/ryansolid/maybe-web-components-are-not-the-future-hfh https://dev.to/ryansolid/maybe-web-components-are-not-the-fu... You can read them directly, but Ryan gives excellent additional context.
        asurty 4y ago
        Thanks for taking the time to find/share these links! Very informative. It sounds to me like most of the criticism's outlined are solvable. Perhaps the people behind the standard should be engaging the framework community more. I wonder if you think web components (and the problem they set out to solve) is wrong from a fundamental/architectural standpoint?