OP 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.
Vue.js vs. React: what happened in 2017
31–40 of 177 posts
Re: Vue.js vs. React: what happened in 2017
#32Re: Vue.js vs. React: what happened in 2017
#33Do Vue templates play nicely with Typescript? That's something I love about JSX -- "it's just JavaScript" is an incredibly sublime feature. I know you can use JSX with Vue but I'm skeptical since it's a first-order feature with React.
Since October (I think) vue single file components work flawlessly with typescript. Can't speak for jsx though.
Re: Vue.js vs. React: what happened in 2017
#34I'm afraid React is eventually turning into Angular. At some point, I felt that Angular is somebody's PhD work exploring arcane computer science concepts, not a piece of software for practical use. React gets closer to that with each year.
Re: Vue.js vs. React: what happened in 2017
#35Earlier 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…
Re: Vue.js vs. React: what happened in 2017
#36I would choose riotjs or vuejs anyday before any facebook's code in my apps.
Re: Vue.js vs. React: what happened in 2017
#37I write ClojureScript A good indicator of if a technology is going to explode, is if emerging language users are excited about it, as good ideas tend to trickle down from the more advanced/research-y ecosystems which aren't as constrained by legacy. So for example React was built by a user of OCaml. ClojureScript early adopted React.js through the Om project in 2013 and there is a growing number of competing React ad…
Re: Vue.js vs. React: what happened in 2017
#38I’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…
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.
Re: Vue.js vs. React: what happened in 2017
#39I'm afraid React is eventually turning into Angular. At some point, I felt that Angular is somebody's PhD work exploring arcane computer science concepts, not a piece of software for practical use. React gets closer to that with each year.
Re: Vue.js vs. React: what happened in 2017
#40I'm afraid React is eventually turning into Angular. At some point, I felt that Angular is somebody's PhD work exploring arcane computer science concepts, not a piece of software for practical use. React gets closer to that with each year.
Can you clarify that comment? What aspects of React's development are you concerned with?