Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)

mangelozzi left a comment (WICG/webcomponents#551)

> Great to see some momentum on this issue ⛵
> 
> **Full disclosure:** I write full-stack but rarely have to navigate these frontend spider-webs since we handle most templating [server-side](https://htmx.org/). From what I understand, Web Components were an attempt to make certain client-side framework features native—though some of those features were arguably [anti](https://gist.github.com/Widdershin/98fd4f0e416e8eb2906d11fd1da62984)-[patterns](https://lea.verou.me/blog/2020/09/the-failed-promise-of-web-components/) [to](https://gomakethings.com/the-shadow-dom-is-an-antipattern/) [begin](https://i.ibb.co/Z1XNTf1f/cgofpd5o2rwb1.jpg) [with](https://github.com/1cg/html-json-speed-comparison). IMHO, we would all be much better off in 2025 if W3C had focused its efforts on completing [HTML](https://intercoolerjs.org/2020/01/14/taking-html-seriously) as [hypermedia](https://htmx.org/essays/hateoas/) rather than chasing framework abstractions.
> 
> `</rant>`
> 

I enjoyed some of your links thanks. I personally think custom web components are great, and am a believer and punter of them. They are so close to being a "complete" toolkit. This issue and reusing style sheets (constructable stylesheets gaining traction) and hopefully html module imports will get us there. 
PS I started with templating back in the day, and the problem with HTMX and friends is it only works if you are in a first world country with a persistent and fast internet connection, and you are probably doing classic CRUD type forms. You can make amazing UI's with custom web components that HTMX cannot realistically achieve.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/551#issuecomment-2660633028
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/551/2660633028@github.com>