4 ms·
Look at this way, angular 16 is now introducing signals, vite support and improving standalone components. Now, let’s compare to Vue, Vue has Standalone compon
by rk06 3y ago
Look at this way, angular 16 is now introducing signals, vite support and improving standalone components.
Now, let’s compare to Vue, Vue has Standalone components, vite support, signals since v3. And fine grained reactivity since v0.
So, one must ask if here things are so good, why stick with angular and wait for everything to stabilise when you can jump ship to Vue now?
Similar argument can be made for react, though I admit hat Angular to react transition won’t be as easy.
And this is in context of newer advancements only. When you take a step back and look, you will see many cases where certain angular issues are only in angular. While rest of the js frameworks are converging
- Jasp3r 3y agoI wouldn't call reactivity in Vue "fine grained". Every object that gets loaded into component state becomes reactive, and every piece of code that touches it gets dragged into a massive internal dependency tree. Vue has blacklisted reactivity, everything becomes reactive (and observed) by default and you can opt-out, while MobX features whitelisted reactivity and is much more fine-grained
- rk06 3y agoI say fine grained as changes in an object will invalidate only that object, and only it's dependencies will be updated. Contrast with coarse grained reactivity I. E. angular, where it must dirty check all "reactive" objects to identify the changed object. As angular can't tell exactly which properties changed.
- cout 3y agoWhat is vite?