30 ms·

Every time I see yet another library of web components I think of the classic XKCD about standards. Apparently there were N web component libraries but none of

Every time I see yet another library of web components I think of the classic XKCD about standards. Apparently there were N web component libraries but none of them were just what ING wanted, so now there are N+1 web component libraries.

spankalee 7y ago
At least these are interoperable with plain HTML, vanilla JavaScript, Markdown, and frameworks. There's value in actual standards.
- Vinnl 7y ago
  Well, you can't just drop them in a React application just yet...
  - ergo14 7y ago
    You can do that for preact,vue,svelte,angular and others. That should tell something.
    - Vinnl 7y ago
      Maybe. But in my case, that tells me that "Web Components is compatible with any framework" isn't necessarily true.
      - ergo14 7y ago
        That makes no sense, they are compatible with react, you just need to write more code to use them. https://custom-elements-everywhere.com/ https://custom-elements-everywhere.com/ I find it interesting that you blame WC not react devs for the fact they don't want to improve your experience.
        Vinnl 7y ago
        Ah sorry, I meant to say "Web Components can just be dropped into any framework" isn't true. Note that you can also use React components in Angular or whatever if you just write more code to use them, but that just doesn't provide enough value to me to overcome the downside. Also note that I'm not "blaming" anyone; just explaining why it's not worth it for me at this point in time to adopt Web Components in my React applications. I very much like the idea of Web Components no longer making us reliant on the web standards process to finally add things like date pickers or typeahead components, but I just don't think it's there yet.
ergo14 7y ago
And they all work together if you want. I see no problem here.
petecarapetyan 7y ago
It's still pretty early, and this won't be anything close to the last one. But with an emphasis on small size and white-label features, it's pretty close to the holy grail. All N component sets usable in any app, w/o respect to some would-be-platform. Nice problem to have. React and friends are looking more and more like oversized polyfills, every day.

spankalee 7y ago

At least these are interoperable with plain HTML, vanilla JavaScript, Markdown, and frameworks. There's value in actual standards.

Vinnl 7y ago
Well, you can't just drop them in a React application just yet...
- ergo14 7y ago
  You can do that for preact,vue,svelte,angular and others. That should tell something.
  - Vinnl 7y ago
    Maybe. But in my case, that tells me that "Web Components is compatible with any framework" isn't necessarily true.
    - ergo14 7y ago
      That makes no sense, they are compatible with react, you just need to write more code to use them. https://custom-elements-everywhere.com/ https://custom-elements-everywhere.com/ I find it interesting that you blame WC not react devs for the fact they don't want to improve your experience.
      - Vinnl 7y ago
        Ah sorry, I meant to say "Web Components can just be dropped into any framework" isn't true. Note that you can also use React components in Angular or whatever if you just write more code to use them, but that just doesn't provide enough value to me to overcome the downside. Also note that I'm not "blaming" anyone; just explaining why it's not worth it for me at this point in time to adopt Web Components in my React applications. I very much like the idea of Web Components no longer making us reliant on the web standards process to finally add things like date pickers or typeahead components, but I just don't think it's there yet.

ergo14 7y ago

And they all work together if you want. I see no problem here.

petecarapetyan 7y ago

It's still pretty early, and this won't be anything close to the last one. But with an emphasis on small size and white-label features, it's pretty close to the holy grail. All N component sets usable in any app, w/o respect to some would-be-platform. Nice problem to have. React and friends are looking more and more like oversized polyfills, every day.