4 ms·

It's a nice idea and I'm glad we can expand the language to differentiate between html web components and javascript web components. That's important because th

It's a nice idea and I'm glad we can expand the language to differentiate between html web components and javascript web components. That's important because the vast majority of use of web components are in the form of javascript web components. The only time I've ever seen HTML web components are on blog posts talking about how you can use web components. Never on an actual website about something besides web components. I want to believe... but reality is stacked against HTML web components. I'm just going to stick to HTML and leave the HTML with dashes to others.

mock-possum 3y ago
I’ve made a couple of big SPAs that use Lit to manage views. I can’t link you to them here without blowing my cover, but honestly I love working with web components, and being able to do it natively rather than propped up by a mound of JavaScript feels good.
- troupo 3y ago
  You're not doing it natively. You're using a framework replete with its own custom DSL, multiple workarounds for issues like SVGs, its own data binding system etc. It's just as native as any other framework under the sun.
  - mock-possum 3y ago
    Sorry, I’ve been working with web components since before they had wide browser support - so now, it’s ‘native’ in the sense that web component is a feature native to the browser, instead of being shimmed / polyfilled in. You can just write web components in an .html file, drag it into the browser, and it works, no build step or servers or external libraries required.
troupo 3y ago
> but reality is stacked against HTML web components. Because they don't exist. "HTML web components" are just HTML, and you don't need components for them. Web Components are useless without Javascript.
mickael-kerjean 3y ago
I do use them on my OSS work (https://github.com/mickael-kerjean/filestash/tree/master/public/components https://github.com/mickael-kerjean/filestash/tree/master/pub...) since I've started migrating away from React to VanillaJS. The app itself is a file manager for every possible file transfer protocol there is (FTP, SFTP, S3, NFS, SAMBA, ....) and is used by many thousands of people

mock-possum 3y ago

I’ve made a couple of big SPAs that use Lit to manage views. I can’t link you to them here without blowing my cover, but honestly I love working with web components, and being able to do it natively rather than propped up by a mound of JavaScript feels good.

troupo 3y ago
You're not doing it natively. You're using a framework replete with its own custom DSL, multiple workarounds for issues like SVGs, its own data binding system etc. It's just as native as any other framework under the sun.
- mock-possum 3y ago
  Sorry, I’ve been working with web components since before they had wide browser support - so now, it’s ‘native’ in the sense that web component is a feature native to the browser, instead of being shimmed / polyfilled in. You can just write web components in an .html file, drag it into the browser, and it works, no build step or servers or external libraries required.

troupo 3y ago

> but reality is stacked against HTML web components. Because they don't exist. "HTML web components" are just HTML, and you don't need components for them. Web Components are useless without Javascript.

mickael-kerjean 3y ago

I do use them on my OSS work (https://github.com/mickael-kerjean/filestash/tree/master/public/components https://github.com/mickael-kerjean/filestash/tree/master/pub...) since I've started migrating away from React to VanillaJS. The app itself is a file manager for every possible file transfer protocol there is (FTP, SFTP, S3, NFS, SAMBA, ....) and is used by many thousands of people