Angular 2 Final Released

Post by awjr » Thu, Sep 15, 2016, 8:15 AM UTC

kayoone wrote: post #21

gkoberger wrote: post #6

As someone who uses Angular 1 currently but would pick React for their next project, I'd love to see a list of reasons why I should use Angular 2 over React. If nothing else, Angular just stranded all their developers, while React has a huge head start on mindshare/plugins/tutorials/etc.

I like the opinionated approach of NG2 over the flexibility of React because it takes a lot of decisions off of me that i am not too interested in when building a new project. I am a full stack developer leaning more towards backend in recent years and i found setting up and finding out about best practices and "what to use" for React a bit tedious, also it changes so much. The last Flux framework i used was alt.js w…

Post by calsy » Thu, Sep 15, 2016, 8:22 AM UTC

choward wrote: post #119

jacobsenscott wrote: post #20

Earlier quoted context omitted.

That's Conway's law for you. All three frameworks were built by meglogcorp, and they all feel exactly the same. It is funny that after the Rails driven success web devs had moving away from J2EE they are falling right back into the same traps - ultra complex bloated frameworks built on a terrible language.

Javascript is definitely a terrible language, but it is the only language for the web unless you consider languages that transpile to javascript. Are you suggesting not using a javascript framework, using a transpiled language instead of javascript, not writing any front end code at all, or doing something ridiculous like turbolinks?

Post by arc_of_descent » Thu, Sep 15, 2016, 8:26 AM UTC

boxctim wrote: post #123

"Loved by Millions" might be overstating things a bit

Post by mcintyre1994 » Thu, Sep 15, 2016, 8:26 AM UTC

lacker wrote: post #129

jasonkester wrote: post #120

Earlier quoted context omitted.

I recently started a new front-end-heavy project and ended up just using Angular 1 instead of React. The decider for me was the amount of tooling that React needs you to have in place just to get up and running. React expects you to do your development on some flavor of Unix, and really doesn't have a sane plan for Windows, so you lose VS.NET and its huge productivity gains. And it needs tools upon tools upon tools t…

And it needs tools upon tools upon tools to set up, whateverify, transpile and pack the files you write into something that can display in a browser. I think this was true six months ago but now there is create-react-app. You might want to try it out - you won't need to whateverify your code, you just need that one tool. Also it works on Windows. https://github.com/facebookincubator/create-react-app I want to edit so…

Post by [deleted] » Thu, Sep 15, 2016, 8:27 AM UTC

0xfaded wrote: post #75

gkoberger wrote: post #6

As someone who uses Angular 1 currently but would pick React for their next project, I'd love to see a list of reasons why I should use Angular 2 over React. If nothing else, Angular just stranded all their developers, while React has a huge head start on mindshare/plugins/tutorials/etc.

For anyone wanting to try react in a side project, scalajs has comprehensive react compatibility and it's just awesome. Only downside is trying to hire Scala frontend devs.