from Hacker News

We moved away from web components – learnings from a Component-First DevTool

by vdelitz on 7/15/24, 3:41 PM with 5 comments

  • by dinoreic on 7/15/24, 5:06 PM

    Long article, and I have to say that I do not agree with ~ 90% said.

    Problem with web components is that they have a few gotchas, one has to solve it he wants to use them effectively. I agree that SSR is a problem, if it is a problem. Crawlers now render JS, I have not see any benefits of SSR for a long time now.

    Also there are a lot of mentions of Shadow DOM. Why would anyone want to use that? It is slower, detached from main process. Just use original DOM and modify it.

    Also, if devs "want!" native components for React, Vue, etc., that does not mean Web components are bad, that only means devs want native components for their FW :).

    I personally hacked my Web components micro FW in 2 weeks, and started to replace Svelte and Rails/StimulusJS with it. I am every happy, but you need to know how to handle gotchas.