Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I would stay with Vue. While the react world is bugger it's mostly made up of competing solutions instead of distinct tasks.

That said, this healthy Vue/Angular/React competition has been great for us devs.



"great" is relative to how much free time you have evaluating all the various alternatives and finding the bugs/missing use cases nobody cares to tell you about up front..


> the bugs/missing use cases nobody cares to tell you about

In the case of fewer frameworks, you would still have these. Arguably more due to lack of competition.

> evaluating all the various alternatives

Pick one of the "Big 3" above. You'll be fine. Largely due to the previous point.


I agree that competition is generally good, but I hate choices so much. I don't even care if Vue is 10 times better than React, I've just spent the last year diving into React and React Native. I've finished 3 big projects and now I'm feeling more confident. And now I get the feeling that I have to throw out a whole bunch of experience and switch to the next big thing.

I think I'm going to dig in my heels this time. React is fine. It's more than fine, I absolutely love working with React, Redux, redux-saga, redux-observable, and a whole bunch of other libraries and patterns that I've finally begun to master after over a year of headaches and frustration. I'm not going to switch to Vue, not even for my next side project.

I didn't personally care about the BSD+Patents license, but you definitely have to keep your eyes and ears open with backlash like this. Even if I think it's a total issue, it might affect my ability to hire employees or even sell my company. So I'm really glad that React is now released under the MIT license.


I don't think anyone's really claiming that Vue is a 'next big thing' to switch to from React. Vue/React/Angular are all competitors of the same generation.


> over a year of headaches and frustration

Seems like an argument against the react ecosystem


A thousand times this. We'll know the JavaScript UI toolkit has started to mature when we can pick up a new tool and not have to abandon all of the other tools we already learned and spend a year getting on our feet in a new "ecosystem".


Don't get me wrong, it was the good kind of struggle where you grow and push yourself. Like going to the gym.

It was the same as any other programming language, framework, or ecosystem. Exactly the same as my experience with Ruby on Rails when I first started doing web development.


If you don't mind sharing, what problem did you have before that was solved by adopting React? (I'm not referring to React Native. It's obvious to me what problem that solves.)


The main thing is having the state flow top-down through your app, so you never have to worry about manually keeping things in sync in the UI. Redux and redux saga have really taught me a lot about programming, and then RxJS and redux-observable completely blew my mind.


I've never found manually keeping things in sync with the UI to be overly burdensome. I guess I've just been lucky.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: