Polyglot, autodidact. OSS author and contributor. Addicted to writing code, seeking my next 'fix'. Love communicating with an audience whose eyes don't glaze over when I get to the 'good parts'.
Web Components are JS. They directly manipulate the DOM similar to the way devs used to w/ document.createElement() but with a hell of a lot more capabilities for efficiency and encapsulation.
For now. Most devs working on WebComponents use some sort of microframework (see open-wc). ITT, I'm one of the very few building WC in a way that requires no build toolchain. If you want to see it in action look up VanillaWC.
Old timer trying to stay young at heart. Started designing for the web back in 97 when I didn’t have a clue. But that’s OK cos hardly anyone else did then either. Much more of a clue now.
Thanks Evan. I will definitely look into VanillaWC more than my cursory look just now.
What has prompted my sudden growth in interest in WC is every-layout.dev. In reviewing their component demos yesterday, and looking at caniuse, I've discovered the following:
Chrome, Firefox and Safari run the components just fine with JS disabled.
Edge runs them too and yet caniuse reports that Edge doesn't support WC. But JS cannot be disabled in Edge, so I presume the components are loading a polyfill in the background (native JS modules are something I'm genning up on).
Polyglot, autodidact. OSS author and contributor. Addicted to writing code, seeking my next 'fix'. Love communicating with an audience whose eyes don't glaze over when I get to the 'good parts'.
It's a WIP for now, I still need to build an entire proof-of-concept site using only WC. Either way, feedback is always welcome in the vanillawc/vanillawc issues.
I've heard of every-layout, guess I need to take a closer look.
A lot of the "WC aren't supported" talk is just FUD from the framework ecosystem. Specifically, React devs love to trash WC b/c React is fundamentally incompatible w/ Standard Web Components.
The reality. The latest Edge evergreen switched to using the same rendering engine as Chrome. Ie Edge should now support everything Chrome does.
The last major blocker is IE, which is a PITA for everybody using ES6, ES modules, CSS Flex/Grid.
Old timer trying to stay young at heart. Started designing for the web back in 97 when I didn’t have a clue. But that’s OK cos hardly anyone else did then either. Much more of a clue now.
Web Components are JS. They directly manipulate the DOM similar to the way devs used to w/ document.createElement() but with a hell of a lot more capabilities for efficiency and encapsulation.
For now. Most devs working on WebComponents use some sort of microframework (see open-wc). ITT, I'm one of the very few building WC in a way that requires no build toolchain. If you want to see it in action look up VanillaWC.
Thanks Evan. I will definitely look into VanillaWC more than my cursory look just now.
What has prompted my sudden growth in interest in WC is every-layout.dev. In reviewing their component demos yesterday, and looking at caniuse, I've discovered the following:
It's a WIP for now, I still need to build an entire proof-of-concept site using only WC. Either way, feedback is always welcome in the vanillawc/vanillawc issues.
I've heard of every-layout, guess I need to take a closer look.
A lot of the "WC aren't supported" talk is just FUD from the framework ecosystem. Specifically, React devs love to trash WC b/c React is fundamentally incompatible w/ Standard Web Components.
The reality. The latest Edge evergreen switched to using the same rendering engine as Chrome. Ie Edge should now support everything Chrome does.
The last major blocker is IE, which is a PITA for everybody using ES6, ES modules, CSS Flex/Grid.
Interesting, thanks.
With regard to IE, I set out my current thoughts in a short Twitter thread, culminating in a link to Sam Thorogood's excellent What To Expect When You're Expecting To Drop IE11 on this here site.