3 ms·
That's a pretty good question. https://github.com/skatejs/skatejs#vs-react https://github.com/skatejs/skatejs#vs-react covers it in a bit of detail. Depending
by jpnelson 10y ago
That's a pretty good question. https://github.com/skatejs/skatejs#vs-react https://github.com/skatejs/skatejs#vs-react covers it in a bit of detail.
Depending on standards will be great in the long run, as over time the need to deliver polyfills will evaporate.
In addition, writing a web component allows integration with any framework (even React! https://github.com/webcomponents/react-integration https://github.com/webcomponents/react-integration ).
- iLoch 10y agoDo you see SkateJS being more beneficial to a React developer than say, Standalone? https://www.npmjs.com/package/react-standalone https://www.npmjs.com/package/react-standalone
- treshugart 10y agoDisclaimer: I'm a contributor. First and foremost, Skate is a web component library designed to give you an augmentation of the specs focusing on a functional rendering pipeline and clean property / attribute semantics. It's about a tenth the size of just React itself, doesn't require any extras and utilises both custom elements and shadow DOM out of the box. React is nice, and if you're can't invest the time to learn something new, Standalone is definitely a good choice. That said, the time it takes to learn Standalone you could have probably learned Skate. In my opinion, right tool, right job; hammer principle etc :) Would be interested to see what jpnelson thinks as well.