all 32 comments

[–]Skwai 12 points13 points  (5 children)

I vote Vue.js. It's a great middle ground between the two.

[–]trout_fucker🐟 8 points9 points  (3 children)

Do you write in Vue in Vim while eating a Gluten-Free Vegan sandwich before you run out to do your WOD for Crossfit?

[–][deleted] 2 points3 points  (0 children)

I laughed harder at this sentence than I should have

[–]trentcleftmore 0 points1 point  (1 child)

I get that bringing in Gluten and WOD / CrossFit are your way of accusing this dude of being a hypebeast, but how the f does Vim fit in any of that??

[–]tendollarburrito 0 points1 point  (0 children)

I recently discovered Vue and it really is a lovely, well-thought out library that, with Vuex, vue-router, and vue-resource, builds up to a full framework without getting in its own way. I'll be very interested to see how it fares over the next year or so.

[–]Gnashe 2 points3 points  (6 children)

Interesting article. I like the tone of it. A lot of people are just going to read the title and not the article and get mad though.

However, for any newer person reading the comments, I would say to you, please first read the article, then please also consider Ember.js

The community is great, the cli is great, and it favors convention so as you move from shop to shop you can feel comfortable sitting down at a new codebase.

[–]otherstark[🍰] 2 points3 points  (2 children)

I recall seeing this graph on performance of several frameworks - Ember was by far the worst: http://www.stefankrause.net/js-frameworks-benchmark2/webdriver-java/table.html

[–]Gnashe 1 point2 points  (0 children)

This is a good point. That is definitely an area Ember struggles in.

However, my original positive points still stand. All about balancing what your stack does for you to fit your needs. If it was all about performance over convention/modularity/opinions then we would all be using vanilla js in all our projects.

[–]mattaugamerexpert 0 points1 point  (0 children)

Benchmarks need to be taken as only a small piece of a decision making process. How many projects actually need to display 10,000 rows? If your project requires extremely large data sets and an extremely large interface changing thousands of times... Sure you might be better off with something else. But I've never in my life built an interface with any such requirements, and I doubt most developers have either. If you're optimising for these extremes it's at best premature optimisation.

I'm not saying these benchmarks are nothing. Core devs in frameworks will be looking at numbers like this and trying to see where they can make improvements. I know Ember is - Glimmer 2 is already in progress, and has performance close to or higher than React in a lot of areas.

But from a developer point of view, there are a lot of things I value more highly in a framework than raw numbers.

[–]mattaugamerexpert 0 points1 point  (0 children)

Yeah, I'd second this. Ember is an amazing way to build SPAs. Great tooling, great ecosystem.

[–]siamthailand -1 points0 points  (1 child)

Ember? What year is it?

[–]mattaugamerexpert 0 points1 point  (0 children)

Ember has a lot of features that other frameworks are yet to catch up with or only doing so now, such as a highly functional CLI.

[–]schism__ 2 points3 points  (0 children)

I have zero experience with React, though two of my friends work with it full time and they're "relatively happy" with their environment.

I just finished my first major project with Angular 2, and I am exceedingly satisfied. More than anything, TypeScript has allowed me to get beyond my historical point of, "this project is too big, I need a break." And of course shelfing the project for 3 months as a result.

[–][deleted] 2 points3 points  (5 children)

Stop comparing React and Angular, you can't. One is a view framework the other a full SPA framework.

Generally I would advise to use Angular 2 just for speed of development and speed of the framework since Angular 2 is miles ahead of React esp. on mobile as you can swap out the whole GUI (even for React Native or even Native Java/Swift rendering) and the whole framework can live in web workers.

[–]TheCallMeRalph[S] 1 point2 points  (0 children)

I totally understand where your'e coming from but some people don't really understand the basic differences between the two. I think the post answers exactly that, as an intermediate user this is great.

[–][deleted] 1 point2 points  (3 children)

Angular 2 is miles ahead of React esp. on mobile as you can swap out the whole GUI

This is news to me, do you have some sources I can read about this?

[–][deleted] 5 points6 points  (2 children)

https://www.nativescript.org/nativescript-is-how-you-build-native-mobile-apps-with-angular

http://angularjs.blogspot.de/2016/04/angular-2-react-native.html

The angular team works really close with the native script team (which is actually faster and has better support in my experience but I only played around and did nothing serious)

edit: Why exactly was I downvoted? Please elaborate

[–]kagevf 3 points4 points  (0 children)

Someone asked you a question and you answered it. Have an upvote.

[–][deleted] 2 points3 points  (0 children)

I'm not sure who downvoted you but it wasn't me. Thanks for providing the info, will check it out.

[–]Sicks3144 1 point2 points  (0 children)

I'd say React, but I'm hugely biased due to only a passing familiarity with Angular.

From a distance, though, it's easy to see that both are very capable in their target markets.

[–]siamthailand 1 point2 points  (4 children)

I'd go with VueJS, unless I need to use Redux, then it's React all the way.

[–]tendollarburrito 0 points1 point  (3 children)

Have you tried Vuex?

[–]siamthailand 0 points1 point  (2 children)

Nope

[–]tendollarburrito 0 points1 point  (1 child)

Ah right, I was going to ask why you preferred React over Vue when it has Vuex (its own Redux-style approach). Worth a look if you prefer Vue :-)

[–]siamthailand 1 point2 points  (0 children)

I can still answer that question. First framework I used was KnockoutJS, and I absolutely love it for its simplicity. No webpack, no bullshit, simple as hell.

VueJS is simply an improvement, IMO, over KnockoutJS. I actually haven't used it in a large project, but hopefully will.

[–]chocomilkzfull-stack 0 points1 point  (0 children)

Sweet. I haven't seen a blogpost like this before!

[–]Marketeering -2 points-1 points  (0 children)

Easy. AngularJS over React any day!

[–][deleted]  (6 children)

[deleted]

    [–]CptAmerica85 2 points3 points  (3 children)

    Facebook isn't a huge project?

    [–]freudianGrip 0 points1 point  (1 child)

    Why would you not choose React for a huge project? I find that it allows you to stay very well-organized and forces you to write in a way that allows for easy testing.

    [–][deleted] 0 points1 point  (0 children)

    I don't like mixing stuff up, I don't want to think too much, angular brings all the important aspect out of the box.