Ask HN: What is your opinion on Web Components?

8 points by regus 5y ago ↗ HN

What do you think of Web Components?

Have you ever used them in production?

Have you ever made something with Web Components rather than using a standard framework (React, Vue, etc)?

Do you think they will ever see wide adoption?

https://developer.mozilla.org/en-US/docs/Web/Web_Components

6 comments

[ 2.0 ms ] story [ 39.3 ms ] thread

shams93 5y ago ↗

The problem is really with safari still not supporting the entire api. If you're writing only for chrome or chrome and firefox and can afford to ignore ios browser users then its a non-issue otherwise you have to offer expensive shims to ios users that undermines the whole purpose of using the webcomponents to begin with.

regus 5y ago ↗

What is missing in Safari? According to the chart on this site Safari is stable:

https://www.webcomponents.org/

cyanydeez 5y ago ↗

https://caniuse.com/custom-elementsv1

mimixco 5y ago ↗

Yes, we're building a production app[0] with them. So far, I think they're great. Far preferable to Angular which we used previously.

[0]https://mimix.io/en/blog/msl-notebook

readonthegoapp 5y ago ↗

I need to look up the difference between generic web components and those that are built with react/vue/etc.

They seem roughly the same.

My take so far as an old school web dev learning this component stuff -- it all sucks

I did enjoy-ish node/express

It seemed relatively straightforward and productive

But I haven't figured out how to make this new front end ts/js/components/frameworks/routers/apis thing productive yet.

I'm assuming that is going to change at some point as I continue spending time, but I admit to being skeptical at the moment

schwartzworld 5y ago ↗

The difference is that to use a React or Vue component, you need to be using React or Vue. Web Components live in vanilla JS land and can be used with any framework, or none at all.