5 ms·

> 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 o

> 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
      AngularJS doesn't use web components as their foundation. VueJS doesn't use web components as their foundation. So you're not asking why. You're ignoring the question and burying your head in the sand.
      - pjmlp 4y ago
        Yeah, because yelling against Web Components in every forum thread is so much more productive. We use them with the frameworks that have first class support, regardless if they are at their foundation or not. Who is actually being ignored here?
        dmitriid 4y ago
        > Yeah, because yelling against Web Components in every forum thread is so much more productive. I'm not yelling. I'm pointing out facts. > regardless if they are at their foundation or not. So why are they not used as a foundation? Why are they used at best as a second class citizen? Why is it these frameworks don't produce web components by default? > Who is actually being ignored here? Framework authors, who have been pointing out the very many deficiencies and shortcomings for years. Most developers who need things like scoped CSS and open-ui.org more than fifteen hundred new standards, each requiring JS to work, barely.
        pjmlp 4y ago
        I only see React framework authors ignoring Web Components. Angular and Vue framework authors considered them good enough to spend development resources on adding support for Web Components, they didn't do it for fun and glory.
        dmitriid 4y ago
        > I only see React framework authors ignoring Web Components. See how you ignore everything I write even though I wrote it in the very first reply: "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." All you keep saying is "oh they support web components only react doesn't support that's the only question why" Full on denial and ignorance. Angular's "support", for example, is slapping on a wrapper, and ignoring everything about web components entirely by loading the angular runtime and everything else Angular behind the wrapper. But sure. Support.

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
    AngularJS doesn't use web components as their foundation. VueJS doesn't use web components as their foundation. So you're not asking why. You're ignoring the question and burying your head in the sand.
    - pjmlp 4y ago
      Yeah, because yelling against Web Components in every forum thread is so much more productive. We use them with the frameworks that have first class support, regardless if they are at their foundation or not. Who is actually being ignored here?
      - dmitriid 4y ago
        > Yeah, because yelling against Web Components in every forum thread is so much more productive. I'm not yelling. I'm pointing out facts. > regardless if they are at their foundation or not. So why are they not used as a foundation? Why are they used at best as a second class citizen? Why is it these frameworks don't produce web components by default? > Who is actually being ignored here? Framework authors, who have been pointing out the very many deficiencies and shortcomings for years. Most developers who need things like scoped CSS and open-ui.org more than fifteen hundred new standards, each requiring JS to work, barely.
        pjmlp 4y ago
        I only see React framework authors ignoring Web Components. Angular and Vue framework authors considered them good enough to spend development resources on adding support for Web Components, they didn't do it for fun and glory.
        dmitriid 4y ago
        > I only see React framework authors ignoring Web Components. See how you ignore everything I write even though I wrote it in the very first reply: "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." All you keep saying is "oh they support web components only react doesn't support that's the only question why" Full on denial and ignorance. Angular's "support", for example, is slapping on a wrapper, and ignoring everything about web components entirely by loading the angular runtime and everything else Angular behind the wrapper. But sure. Support.