[📖] Create "Qwik web components" page about qwik

[devinrhode2]

Copying my comment from the other thread:

I have googled “qwik web components” a few times now, and for the second time, I am looking at this thread.

I would love to be able to roll with Qwik City as a meta-framework but still be able to use some react or solid or vue components. Full-ish react interop would make migration of existing apps truly feasible for most projects.

Perhaps we need a fresh take on web components that support ssr, a sort of universal “RSC”. Cc @mhevery

[PatrickJS]

The issue is that Qwik is optimized for the web, unlike web-components. It’s ironic, considering “web” is in the name of web-components. Qwik only needs to download code that the user will actually use, so by definition, none of the web-components, if made in Qwik, will need to be downloaded to run (assuming most are presentational components). If the primary benefit is having a centralized design-system, that’s acceptable. However, if most components are web-components, the benefits are questionable. You still gain from the Qwik wrapper, but you’re always going to include the design-system web-components javascript on the page. Either way, it’s still better than other frameworks, where you need to include even more js.