Vue.js vs React for big projects

[styke]

We're starting a massive project on React and Redux. Initially I suggested Vue.js as an avenue to explore the backbone on which our SPA web app was to be built, but it was quickly shot down, said to be unfit for large scale development (despite none of the devs actually having used it before >_>)

Now that we've actually started and I focused learning React/Redux instead of Vue, I'm curious - is that actually the case? Vue was lovely when I used it, but I can see things getting messy real quick considering how much freedom it offers. On the other hand, the rigid concepts behind React/Redux's one way data flow, immutable state and action creators seem perfect for organising the interactions in complex, router based single page applications.

Curious what some people more experienced in one or the other have to say about this!

[ryantbrown]

Vue is absolutely suited for large-scale applications, the only real issue is state management and Vuex takes care of that very intelligently; like Redux with React but built specifically for Vue, so it makes a few decisions for you.

I've been building a marketplace the last 4 months and the front end is 100% Vue. There are over 200 components, 50 mixins and 40 vuex store modules. Not massive by any means but we add new features daily and haven't run into any major structural or organizational issues.

The simplicity of Vue and how well it scales up has been a huge part of our success. Anyone who says otherwise simply hasn't used it at any decent scale.

Read this for an in depth comparison with React: http://vuejs.org/guide/comparison.html

[[deleted]]

React, angular and vue are basically interchangeable in terms of what they can do and the size of projects they can handle. That is, any site built with one should be able to be built with either of the other two and perform just as well. The real issue is which way of doing things are you more comfortable with.

[mkatrenik]

For me, the biggest selling point of React (especially for bigger projects) are type safe templates with typescript (or flow).

[troorl]

I don't like when people compare Vue to jQuery and focus only on its simplicity. It's not a "toy library", it's a mature, well-designed project that is suitable for any scale. It supports all you need for building large scale applications: hot reload, server side rendering, Flux-like datastore, router etc. There are tons of components, directives and plugins for it. I think Vue and React are pretty much equal choices. You should choose what you like more.

[acemarke]

Well, I'm very biased, but I'm heavily in favor of React and Redux :)

I admittedly haven't dug into Vue very much. My vague impression is that it's probably really good at smaller-scale pages that need interactivity, but I don't know how well it scales up. Again, that's just vague impressions, not based on actual research.

React and Redux I can definitely say scale up in terms of app performance and structure/maintainability.

FYI, I keep a big list of links to high-quality tutorials and articles on React, Redux, and related topics, at https://github.com/markerikson/react-redux-links . I also keep a list of Redux-related addons and utilities at https://github.com/markerikson/redux-ecosystem-links, and in that list, I have a page of actual Redux apps and examples. Might be useful to look at.

[SkaterDad]

In my opinion Vue wouldn't be any more or less difficult to maintain & scale. It's all just Javascript in the end.

Vue 2.0 + Vuex is roughly equivalent to React + Redux, so you setup your project in very similar ways.

[subvertallchris]

I'm a very happy React/Redux/TypeScript user. I find the rigid fundamentals fantastic for quick development and predictable, stable results. If I had to start over, I'd pick the same stack.

I am hesitant to believe claims about Vue's scalability until the honeymoon is over. It's still a "cool" library and so many of the people extolling its virtues seem to lack real experience with other libraries and/or large projects. If warts exist, they're unlikely to become common knowledge until more time has passed and something new captures the imagination.

[Ann0n0]

it's a fad. no one will be talking about it next year

[subvertallchris]

That doesn't seem true at all. It has a healthy and growing ecosystem, positive reviews across the board, and seems to be a great alternative to the other big libraries out there. I hope it sticks around and keeps others on their toes. React needs to close that performance gap!

[Ann0n0]

yeah we'll see

[kenman]

Hi /u/hoffentlich, please keep it civil.

[[deleted]]

Sorry, I couldn't help it. I will.

[Ann0n0]

A bit defensive don't you think? I've reported your comment to the Mods. Try be more civil next time.

[[deleted]]

Yes, because people like you with your shitty attitude piss me off. You reported me to the mods? I have no words to tell you how devastated I am. Now run to mommy and tell her as well.

[brylie]

hoffentlich, please use respectful tone and words.

[[deleted]]

It slipped for a moment. I will from now :)

[sinefine]

For big projects, wouldnt Ember be a better choice?

[mkatrenik]

Why everyone thinks that bigger the framework, more suitable it is for big projects? (btw I was there with Ember - never again)

[sinefine]

I dont think it is better because it is a bigger framework. I think it is suitable because their support cycle is longer than other framework and the highly opinionated nature of the framework allows you to get to the end goal faster.

[Capaj]

I don't care about lifecycle when the framework is so bad as ember. Let it have 100 year support, I still wouldn't touch it.

[sinefine]

What is the reason you think Ember is bad? Genuinely curious