React IMHO is good enough that I don't want to change framework/basic frontend technology again.
Agreed, it’ll take another paradigm shift to switch to something else.
Vue.js vs. React: what happened in 2017
41–50 of 177 posts
Re: Vue.js vs. React: what happened in 2017
#42Why in earth people would like to to use anything from facebook in they business ? Why do you trust they licensing ? I would choose riotjs or vuejs anyday before any facebook's code in my apps.
You apparently aren't keeping up with the latest about riotjs: https://github.com/riot/riot/issues/2283
I wouldn't feel confident picking that as my company's future.
Re: Vue.js vs. React: what happened in 2017
#43Earlier quoted context omitted.
I agree. We still admire Vue.js after using it for more than a year and writing hundreds of lines of Vue.js code every day. No chance I would choose React+Redux in cases when I know I need quick progress on my web project - Vue.js allows you to be very productive, cutting corners in the right places, while still keeping the reasonable code quality, and writing very little of boilerplate.
MobX+React would be just like Vue, but with the benefits of the larger React ecosystem and full type checking with typescript/flow, and the drawback of mandatory build tooling.
i've been wondering about that too, and would love to see some write-ups of people that have react+mobx for at least a few months if not more, how it worked out for them, plusses and minuses.
Also tutorials for react+mobx.
Re: Vue.js vs. React: what happened in 2017
#44Re: Vue.js vs. React: what happened in 2017
#45OP predicts with absolute certainty vue "will become dominant" next year many times. Also OP has skin in the game to justify to his team that vue was the correct choice. Nice as an opinion piece but too many red flags to be considered fair and unbiased.
Huh? OP said the power of the React ecosystem and change in license will keep it on top in 2018 and that if they were starting from scratch they probably would have used React for their website.
Re: Vue.js vs. React: what happened in 2017
#46I’m the founder writing code (but not the only technical person) for my three person startup. In October I started migrating our MVP from server side templates to Vue, given we had direction and traction on a product line that justified the time investment. It’s turned out to be a great decision (although likely one that could have been made with react as the choice as well). My “success story” is how Vue helped me t…
What is a turbolink?
Re: Vue.js vs. React: what happened in 2017
#47Earlier quoted context omitted.
Since October (I think) vue single file components work flawlessly with typescript. Can't speak for jsx though.
It works in the part of your .vue file, but not the part.
Ah, that's a bummer. Vue Templates seem wildly regressive to me -- I can't fathom going back to stringly-typed Handlebars wrangling after using JSX/TSX.
After looking into this further it seems like Vue Templates also differentiate between values and components. In React I often write components which can take in either: a good example is text which the consumer might want to format. You can easily write the component so that they pass in a string or a element.
Vue has a lot of good ideas but the templates are almost a non-starter for me.
Re: Vue.js vs. React: what happened in 2017
#48React IMHO is good enough that I don't want to change framework/basic frontend technology again.
Agreed, it’ll take another paradigm shift to switch to something else.
Not necessarily.. I wonder had react not been backed by FB, it certainly would have had a beating in its popularity given lighter and arguably faster alternatives like vue. Remember, performance was one of the main argument React had when compare to Angular. Now since performance is no more a differentiating factor, developers might look into other aspects like better ROI in short and long term..
Re: Vue.js vs. React: what happened in 2017
#49Earlier quoted context omitted.
Can you clarify that comment? What aspects of React's development are you concerned with?
First, probably was their approach to implicitly require use of Observable objects everywhere. Second, use of arcane CS lingo and authors writing 10 pages long pages on every known MVC model, FLUX, SCHMUX and etc with weekly regularity. Third, during transition to Fiber, they went on gigantic increase of complexity by introducing a lot of what can be said to be heuristic rules, and all for non-guaranteed, minor perfo…
1) I've been using React for 4 years and never used observables, what do you mean?
2) Please clarify what you mean by this.
3) By all accounts, the fiber codebase is much simpler than the stack codebase, performs similarly and opens up some exciting new possibilities.
Re: Vue.js vs. React: what happened in 2017
#50[deleted]