It’s not obviously faster, but it’s been benchmarked to be faster. https://youtu.be/nXCSloXZ-wc
You can skip to 29:34 for the performance demo.
232 karma · joined April 25, 2011
It’s not obviously faster, but it’s been benchmarked to be faster. https://youtu.be/nXCSloXZ-wc
You can skip to 29:34 for the performance demo.
When you write templates, you get more room for optimization. Glimmer engine compiles templates to binary bytecodes to bypass JavaScript parsing. Vue3 inlines component fragments as part of the compilation step.
Apple News link bypasses the paywall
If you like that, why not go with Ember?
Atomics offers single level specificity thus providing a strategy to combat the specificity problem that plagues many projects.
They are single purpose and infinitely composable, which complements very well with component oriented architecture that's popular today.
They are localized to single DOM node. When combined with its single purpose nature offers fewer surprises when making changes to your style sheet. For example, when you add a margin 15 Atomics to a DOM node, it is very hard to accidentally add another margin 15 somewhere else. Versus if you add a label class, it is much easier to accidentally add another label class and cause unintended consequences.
The #2 person contributes only about 1% compared to the #1 person.
Compare to React's same graph: https://github.com/facebook/react/graphs/contributors?from=2...
The #2 person is at about 50% of the #1 person.
Compare to Ember's same graph: https://github.com/emberjs/ember.js/graphs/contributors?from...
The #2 person is at 75% of the #1 person.
Since requestIdleCallback leaves the scheduling out of your hand, how do you ensure nodes are still updated when you need it? Like tests?
No, it did not catch on.
Component architecture, check. Two way binding, check. Optional type, check. IDE, check.
My favorite, typed components, check.
Also checkout Ember twiddle [2] to play around first without installing a thing. You can add libraries and even other Ember adding through twiddle.json
The only possible tie that Ember with Rails is that it used to bundle ActiveRecordAdapter with Ember data. It is now separated into another project possibly due to this exact reason.
[0]: http://sanestack.com