The journey from giving up React.js in favor of Vue.js
1–10 of 28 posts
Re: The journey from giving up React.js in favor of Vue.js
#2A poorly done React component (mixing props and state?) and what looks to be a poorly done Vue component (with some jQuery lib thrown in?), are the basis of the opinion? Seems weird.
Re: The journey from giving up React.js in favor of Vue.js
#3A poorly done React component (mixing props and state?) and what looks to be a poorly done Vue component (with some jQuery lib thrown in?), are the basis of the opinion? Seems weird.
Yeah, pick any framework that you don't know how to use properly, drop it for another framework that you don't know how to use properly, write a post on medium about it, repeat.
Re: The journey from giving up React.js in favor of Vue.js
#4Seems more like they threw their hands up in frustration and went with something that was more immediately understandable to them.
I haven't used Vue yet, but I'm curious how nice it is to develop with after the codebase has grown significantly - I remember Angular 1.x had that same "magic" that made it easy to appreciate and pick up, but ended up being a huge headache after writing production code with it for over a year.
And really, there's a reason why React isn't designed to work well with jQuery. That's one of its biggest strengths - writing code declaratively and letting it figure out what the correct state/DOM should be. I can't imagine trying to write a complex SPA and modifying the DOM directly - that was the reason Facebook came up with React to begin with.
Re: The journey from giving up React.js in favor of Vue.js
#5I find Vue to be such a breath of fresh air. All I wanted out of React was shadow DOM and then it went and turned into this whole cultural movement thing.
Re: The journey from giving up React.js in favor of Vue.js
#6Was on the front page for some reason... what is it with the abysmal quality articles advocating vue.js?
Re: The journey from giving up React.js in favor of Vue.js
#7> It’s just a library, so if you want to make use of a fully featured framework, the React guys invented Redux
This is wrong; Redux is not a framework, it's just a technique for managing state.
Re: The journey from giving up React.js in favor of Vue.js
#8> ...jQuery it’s still a thing... for example a grid with a subgrid that supports bootstrap and is easy to change...
No way. Angular made me leave jQuery forever. React made it even simpler to create components. People should still learn jQuery and its internals because of its simplistic (api) interface and internal code.
I like Vue too, because its so easy to develop a lot in a few hours. But as code grows and complexity grows - Vue loses its simplicity and I end up migrating to React.
EDIT: Reading the article it feels like they lack expertise in both JS and CSS (and Thinking in React way pushed them over the edge)
Re: The journey from giving up React.js in favor of Vue.js
#9That Vue component, from a glance, seems less readable, more complex, and more stateful than the given (poorly written) React component. And none of the arguments against React really make sense to me (ES6 is not complicated, JSX is light syntactic sugar, and you probably don't need FLUX to start...).
It seems like the _main_ problem they were having was that they were trying to graft React onto an environment based on jQuery and then realized that it made things complicated. That's not a knock against React, that's just shooting yourself in the foot and blaming the gun.
Re: The journey from giving up React.js in favor of Vue.js
#10Am I missing something? The example React and Vue components they provide seem to be completely different components, and the React one is missing most of the code.