3 ms·
It's like the difference between TypeScript and ES6. The goals are intentionally aligned, and as the underlying platform adds support for the constructs that p
by altano 11y ago
It's like the difference between TypeScript and ES6. The goals are intentionally aligned, and as the underlying platform adds support for the constructs that power TypeScript, it can continue to delegate more and more to the underlying platform.
Knockout custom elements, for example, are extremely similar to web components. As support for web components proliferates, Knockout can keep the same framework API but use web components under the covers.
- velmu 11y agoI look forward to using Web Components myself, regardless of the actual method we'll end up creating them. Just like jQuery has become "useless" in many cases, it took us a long way to where we are today. Sure we'll need to worry about SEO, etc. but Googlebot (and others, hopefully) are already quite capable of executing Javascript. To me the Riot.js web component syntax seems very natural to write - more so than JSX. Here's an example: https://www.symfony.fi/entry/build-a-web-component-with-riot-js-and-yandex-maps https://www.symfony.fi/entry/build-a-web-component-with-riot...