Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why we moved from Angular 2 to Vue.js and why we didn’t choose React

medium.com

Post reply on HN
Print view View original

81–90 of 151 posts

Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React

#81

Post by gruez »

rocky1138 wrote: post #52
christophilus wrote: post #37

Earlier quoted context omitted.

If you know only JS, JSX is much easier to pick up than some proprietary templating language. How do I do an if, a loop, a map, ... any code at all? In JSX, the answer is squiggly-brackets and regular old JS code. In Angular's templating system and Vue's, you've got to relearn all of these and more.

> proprietary templating language Isn't that exactly what JSX is?

I think he meant that in vue.js/angular you have to learn a bunch of proprietary tags for each construct (if, foreach, etc.), whereas in JSX all you need is plain old javascript.

Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React

#82

Post by chrisco255 »

orclev wrote: post #76
chrisco255 wrote: post #60

Earlier quoted context omitted.

Is that still true to this day? JS has exploded in popularity and utility in the last few years. Even Stanford and other high quality CS schools are teaching JS now.

Yes, it's in many ways exactly that popularity that's the problem. The ratio of good to mediocre programmers hasn't really changed any, but now there's a whole lot more JS devs out there, so finding the good ones is an exercise in wading through a sea of mediocrity. For better of worse, the Java developer ecosystem does a better job of filtering out the mediocre devs, and generally once you reach a certain level of e…

The problem I tend to see there though is back end developers often lack good UI skills.

Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React

#83

Post by wambotron »

I still say Mithril (https://mithril.js.org/) is where it's at. I am at a company now that uses Angular 4.x and I'm not impressed with it. IMO, it's a way to make JS seem more like Spring/Java (especially with Typescript) rather than understand how JS works and use it as it is.

Not to mention the learning curve even for senior developers. Mithril took me maybe 30 minutes to understand. The entire source (https://github.com/MithrilJS/mithril.js) is easily read in a few hours. They have multiple committers and an active gitter chat room for any problems. Plus you can use JSX if you like it that much. And it has a nice license.

More folks need to try it out.

Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React

#85

Post by ageofwant »

ArchReaper wrote: post #29

Maybe my viewpoint is too 'elitist' or something, but I have a hard time taking this seriously when one of the chief complaints of Typescript is that it is too "difficult" It really makes me question the validity of the rest of the points.

Typescript is not difficult, it just solves problems almost no one has, and makes you do silly things that slow you down. Difficult like in 'petulant child' difficult, not 'what woman want' difficult.

Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React

#86

Post by bojanvidanovic »

I envy how some companies can migrate from one to another framework like that. Beside that, TypeScript is just fine once you get more time with it, you don't need to type everything. On the other side I find Angular more stable framework on the long run.

Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React

#87

Post by seanwilson »

christophilus wrote: post #39
ashark wrote: post #31

Earlier quoted context omitted.

We went from anything like JSX getting you laughed out of the room (LOL 'onclick' properties, hello, 1998 called! Also code doesn't belong in markup, so markup certainly doesn't belong in code, are you insane? Templates! Separate style!) and sensible, healthy skepticism of workflows like "compiling" not-html to still-not-HTML to eventually generate HTML at runtime, to all of that being just fine and anyone not immedi…

It's because it flew in the face of commonly accepted best practices. It felt like a return to PHP/ASP days of old. But in reality, once you use it, you realize it's not that. It's a good abstraction. It puts concerns in the right place. Now, when I have to write something in any .erb file, it's like pulling teeth. JSX + React is a very good view-layer and component abstraction.

> It's because it flew in the face of commonly accepted best practices.

People need to stop blindly following current "best practices" because they change all the time. Weigh up the pros and cons yourself. I personally don't see any difference with doing a loop in JSX and doing a loop in HTML using special tag attributes.

Best practices for web app UIs have changed dramatically as we've went from e.g. server side only logic -> jQuery/AJAX based UIs -> Backbone -> Angular 1 -> React. This clearly shows we've no idea what the "best" way to do things is yet.

Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React

#88

Post by jordache »

The author made some really weak arguments.

In his comparison matrix, why was Reactivity a criteria? Why did Angular score a "Kind-of"? Reactivity is just another word for the framework's underlying change detection logic. Obviously all of these frameworks have that. The fact that he put the term "reactivity" up on a pedestal and rated angular down tells me the lack of understanding on the author's side

Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React

#89

Post by [deleted] »

christophilus wrote: post #37
che_shirecat wrote: post #20

Earlier quoted context omitted.

> It should take no more than 20 minutes to learn JSX. it should, but in practicality, for most front-end devs especially junior ones, it's not. Moving Angular 1 devs to Vue gets actual work going 3-4 times (anecdotal experience) quicker than with React. For most smaller shops/startups Vue is almost always a better idea - it's much easier finding devs (especially remote/<100k comp ones) with previous Angular 1 experi…

If you know only JS, JSX is much easier to pick up than some proprietary templating language. How do I do an if, a loop, a map, ... any code at all? In JSX, the answer is squiggly-brackets and regular old JS code. In Angular's templating system and Vue's, you've got to relearn all of these and more.

[deleted]

Re: Why we moved from Angular 2 to Vue.js and why we didn’t choose React

#90

Post by kumarvvr »

sayurichick wrote: post #24
kumarvvr wrote: post #19

Vue seems to be less taxing on the mind. Compared to React, I feel Vue is more easy to build with. Just my 2 Cents

I agree. Having used both on small projects I was able to get started and finish quicker on Vue. That being said, I use React more because of the larger community, (easier to find answers, and components) as well as more jobs for React vs Vue. Also, Fiber introduces better animation performance, which i'll eventually use.

Things have become easier with create-react-app though.
Post reply on HN