TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: Is 2022 the year of web components? [front end web dev]

3 pointsby okareamanover 3 years ago
I&#x27;ve been out of the loop for awhile, but back in 2017 I was a big fan of Polymer by Google (web components utilizing shadow DOM.) At the time there was a feeling you didn&#x27;t need frameworks if you had components you could use like html tags.<p>In 2021 I got back into it:<p>I took a look at Blazor. Ok, that&#x27;s just web components, where the file name is the component name.<p>I took a look at Svelte. Ok, that just web components with reactivity. Svelte looks like the inspiration for Blazor.<p>I took a look at Angular. They have components now or did they always have components?<p>I took a look at React. Look, they&#x27;re starting to use Polymer type components inside React components.<p>I took a look at web components, not longer called Polymer it seems, and wow, they&#x27;ve made a lot of progress. Salesforce.com is a big user (a company I respect for their tech) and Google itself is a big user. Google says Web Components are everywhere and I&#x27;m using them a lot without knowing it.<p>So have Shadow DOM components arrived?<p>https:&#x2F;&#x2F;developer.mozilla.org&#x2F;en-US&#x2F;docs&#x2F;Web&#x2F;Web_Components

2 comments

travisdover 3 years ago
I don&#x27;t actively follow web components, but as someone who follows the React space reasonably well, I don&#x27;t get <i>any</i> sense that things are shifting towards web components (at least in the sense of replacing React). React&#x27;s docs[1] argue that they solve different problems (obviously that&#x27;s potentially biased, but I still find it reasonably compelling). I think the most likely outcome is that some things will be shipped as web component libraries that can be easily consumed within various frameworks (e.g., I could envision Stripe shipping a webcomponent library instead of a React specific library).<p>[1] <a href="https:&#x2F;&#x2F;reactjs.org&#x2F;docs&#x2F;web-components.html" rel="nofollow">https:&#x2F;&#x2F;reactjs.org&#x2F;docs&#x2F;web-components.html</a>
评论 #29804085 未加载
评论 #29753138 未加载
dannyeover 3 years ago
2017 to 2022, that is 5 years. But its 4 companies (Apple, Google, Microsoft &amp; Mozilla) that all need to agree in setting this Web Components standard. So it <i>can</i> feel like slow progress. But.. once a standard, it will will last for another 27 JavaScript years. And anyone who has been in this &quot;Internet&quot; business for that long can tell you how valuable that is. Remember IE once had 90% market share.. guess how much market share Facebook will have in N years time. PS. The WHATWG is by invitation only, and we all wonder if those 4 companies will invite Facebook.<p>It is NOT about Technology, it is about Who creates Technology.