If you did, are you considering switching back to React? How is your experience with Vue? What does Vue do better than React? What does React do better than Vue?
I'm switching from Vue to React because I find it really kludgy to have to call Vue.set to declare new reactive properties at runtime.
Its also a bit nicer in that React tends to follow ES standards like ES6 classes for components, instead of exporting a POJO for your component. In vue you often have to use function() instead of fat arrow syntax because of the context of "this". With react you used to have lots of .bind(this) boilerplate, but now we have shorthand property syntax. Vue also mixes props & state, where as React keeps them separate. React implements certain lifecycle methods like componentShouldUpdate() whereas Vue doesn't because the creator thinks it would complicate the API, meanwhile there's known issues like between Vue.js & HTML5 content editable due to this lack of lifecycle method.
Vue is easier to get going & much faster to develop in initially, lower learning curve, and friendlier API.
Declaring properties at runtime is an antipattern.
You never need to use function()
Props and state are absolutely not mixed. Props are inherited and immutable by default.
Content editable doesn’t fit in with the vue paradigm but you can easily abstract that section out of vuejs. If you dom is not dictated by your data, then a render function makes little sense.
> Declaring properties at runtime is an antipattern.
That's a pretty bold statement & I won't argue, but either way that's an opinionated decision of the framework. React is less opinionated & doesn't care what you use for your state. Vuejs is opinionated, they don't care about working well with Redux or other state management libraries because they already have their own, Vuex, which is pretty nice for the most part.
> Props and state are absolutely not mixed
a prop called "foo" & data/state param called "foo" are both accessed at this.foo, its no longer obvious what would happen if I would try to mutate this.foo. It mutates the data/state, not the prop, so now this.foo refers to the value in the data/state, which has a different value from the
prop "foo" which can no longer be accessed at this.foo
> You never need to use function()
See this page which says "Don’t use arrow functions ":
> you can easily abstract that section out of vuejs.
Yeah you can, by not using vuejs. React has escape hatches to get out of your way, so you could continue to use it in that scenario thats part of why im switching back from vuejs to react.
Could you expand a bit on shorthand property syntax or provide a link to somewhere I could read more? I'm still doing a lot of .bind(this) in many places and I'm looking for an alternative.
Yes, we had been planning to switch from Angular 1.x to React but our legal team determined it was too risky. The licensing issue was cleared up (I think) right after that decision was made
That is really a shame. React is hugely better than Angular 1.x in just about every way in my opinion.
When we switched productivity went through the roof and the site rendered faster.
That's not actually why I switched though. I switched because of the whole mess with Angular 2.x planned lacked of backwards compatibility. It was the nail in the coffin for Angular for me.
Readit News
Its also a bit nicer in that React tends to follow ES standards like ES6 classes for components, instead of exporting a POJO for your component. In vue you often have to use function() instead of fat arrow syntax because of the context of "this". With react you used to have lots of .bind(this) boilerplate, but now we have shorthand property syntax. Vue also mixes props & state, where as React keeps them separate. React implements certain lifecycle methods like componentShouldUpdate() whereas Vue doesn't because the creator thinks it would complicate the API, meanwhile there's known issues like between Vue.js & HTML5 content editable due to this lack of lifecycle method.
Vue is easier to get going & much faster to develop in initially, lower learning curve, and friendlier API.
Why You need to do this that often? We have a lot of moving parts in app, but just a few `Vue.set` calls.
Declaring properties at runtime is an antipattern.
You never need to use function()
Props and state are absolutely not mixed. Props are inherited and immutable by default.
Content editable doesn’t fit in with the vue paradigm but you can easily abstract that section out of vuejs. If you dom is not dictated by your data, then a render function makes little sense.
That's a pretty bold statement & I won't argue, but either way that's an opinionated decision of the framework. React is less opinionated & doesn't care what you use for your state. Vuejs is opinionated, they don't care about working well with Redux or other state management libraries because they already have their own, Vuex, which is pretty nice for the most part.
> Props and state are absolutely not mixed
a prop called "foo" & data/state param called "foo" are both accessed at this.foo, its no longer obvious what would happen if I would try to mutate this.foo. It mutates the data/state, not the prop, so now this.foo refers to the value in the data/state, which has a different value from the prop "foo" which can no longer be accessed at this.foo
> You never need to use function()
See this page which says "Don’t use arrow functions ":
https://vuejs.org/v2/guide/instance.html#Data-and-Methods
> you can easily abstract that section out of vuejs.
Yeah you can, by not using vuejs. React has escape hatches to get out of your way, so you could continue to use it in that scenario thats part of why im switching back from vuejs to react.
https://www.fullstackreact.com/articles/use-property-initial...
When we switched productivity went through the roof and the site rendered faster.
That's not actually why I switched though. I switched because of the whole mess with Angular 2.x planned lacked of backwards compatibility. It was the nail in the coffin for Angular for me.
Dead Comment