Live data from Hacker News

Vue.js vs. React: what happened in 2017

pixeljets.com

161–170 of 177 posts

Re: Vue.js vs. React: what happened in 2017

#161

What I find most interesting in these results is the satisfaction percentage i.e. (Used it before and would use again) / (Used it before and would use again + Used before and would not use again). - In 2016: React - 91% satisfaction Vue - 91% satisfaction Angular 2 - 65% satisfaction No framework - 65% satisfaction Ember - 50% satisfaction Angular - 40% satisfaction Backbone - 31% satisfaction - In 2017: React - 93%…

What I find odd/funny is that a significant chunk of people have "never heard" of using no framework. Either it's a mistake or there are that many people who've never just written some JS code.

Re: Vue.js vs. React: what happened in 2017

#162

Earlier quoted context omitted.

This is my reasoning too. Until someone creates a better reagent and reframe and renatal I'm gonna stick with React

What do you find missing in Reagent currently that works better in React?

Nothing (?!).

Re: Vue.js vs. React: what happened in 2017

#163

Earlier quoted context omitted.

What do you find missing in Reagent currently that works better in React?

Nothing (?!).

So what would you expect to see in a better reagent and reframe and renatal that would make you switch from React?

Re: Vue.js vs. React: what happened in 2017

#164

Having used all of the big three. Am I the only one who likes and prefers Angular?

Curious—what makes you prefer angular?

It's very well structured, easy to understand, batteries included, lends itself well to maintainability and scale.

When working for a company with staff below me who had very basic understanding of JS (having just done HTML/CSS/JQuery, had no idea what a promise was), there was almost no learning curve with Angular. The hardest part was understanding what a component was, then learning the folder structure.

Angular's seamless use of templating, the built in support for CSS pre-processing and simplicity of uni-directional databinding had the entire team pick it up and be productive almost immediately.

Using decorators to declare inputs/outputs on dumb components is clear, readable and easy to understand.

Class based components are also very clear.

Some say TS is annoying and all power to you, but using types is optional. Personally, TS has allowed me to save on some test cases by virtue of the compiler catching those issues. Plus there is a comfort in quality intellisense.

Vue is cool, it's like a less opinionated Angular. In my opinion, it's strength is its ability to be dropped into any project, giving you client side components and databinding irrespective of your stack. However I have experienced growing pains in larger projects as a result of people over complicating simple solutions.

I am still relatively inexperienced though, and I intend to spend more time with Vue to see if I can't like it more. I'm sure all of my concerns are addressable. So far though, Angular has treated me very kindly, both in large and small scale projects.

Re: Vue.js vs. React: what happened in 2017

#165

Earlier quoted context omitted.

I couldn’t disagree more. Unless your team have Super in depth knowledge of angular then it’s the wrong choice. It’s defaults to progagate changes cause rendering perf issues that are so frustrating to fix. Out of the box react or vue performs better than angular hands down. I hate that after learning angular 2 I realise I should not followed tutorials and advice and just switched all the defaults off on classes and…

I don't know what convoluted patterns you where implementing, but out of the box, the default change detection in angular is performant, esp if you start to leverage observables and the async pipe (to eliminate the need for component onDestroy maintenance tasks). It's a joy to use. Yes Angular provides a lot more options than react or vue, and maybe confusing given the scope of what's possible. However, after the ini…

The default change detection can cause the whole page to redraw. Especially if you have a lot of data. It gets even worse.

Re: Vue.js vs. React: what happened in 2017

#166

Earlier quoted context omitted.

Nothing (?!).

So what would you expect to see in a better reagent and reframe and renatal that would make you switch from React?

No, what I mean is that I'd only switch from reagent with react for a better-than-reagent fw based on vue.

Re: Vue.js vs. React: what happened in 2017

#167

Earlier quoted context omitted.

So what would you expect to see in a better reagent and reframe and renatal that would make you switch from React?

No, what I mean is that I'd only switch from reagent with react for a better-than-reagent fw based on vue.

Ah sorry, I completely misread your original comment. :)

Re: Vue.js vs. React: what happened in 2017

#168

Earlier quoted context omitted.

I don't know what convoluted patterns you where implementing, but out of the box, the default change detection in angular is performant, esp if you start to leverage observables and the async pipe (to eliminate the need for component onDestroy maintenance tasks). It's a joy to use. Yes Angular provides a lot more options than react or vue, and maybe confusing given the scope of what's possible. However, after the ini…

The default change detection can cause the whole page to redraw. Especially if you have a lot of data. It gets even worse.

it's pretty much the same change detection logic across all of these frameworks. Immutable data is key to performant change detection. Angular provides the ability to bind template to immutable state data so the framework can provide the most performant change detection

Re: Vue.js vs. React: what happened in 2017

#169

Earlier quoted context omitted.

The default change detection can cause the whole page to redraw. Especially if you have a lot of data. It gets even worse.

it's pretty much the same change detection logic across all of these frameworks. Immutable data is key to performant change detection. Angular provides the ability to bind template to immutable state data so the framework can provide the most performant change detection

Except it's not the same across all these frameworks.

If I build a grid with 15 columns and 3500 rows (actual issue faced) which contains 3 characters in a cell and a menu when clicking on the cell.

Out of the box Angular took ~8 seconds to make it appear on the screen.

Vue and React were both less than 1 second.

If I changed the value of a cell, then Angular would redraw the entire grid, Vue and React just updated the cell.

You know what the Angular gitter room told me to do... turn off change detection...

Changing it to 1 way binding resolved the rendering time and made it on par with the other 2, but it's still frustrating, especially when the same example in Angular 1 worked in less than 1s with 2 way binding.

Re: Vue.js vs. React: what happened in 2017

#170

Earlier quoted context omitted.

JSX is also neither HTML nor JavaScript.

> JSX is a thin XML-like DSL on top of Javascript ^ this. It directly translates to `React.createElement`. This is also why everything inside {} is pure Javascript including things like proper `this` etc.

Ok, so they both let you use something more like what you already know, except neither of them are technically JavaScript or HTML. Glad we established that. I think the understated bikeshed color here is that VueJS allows you to use jade/pug syntax instead of HTML.
Post reply on HN