Hacker News Reader

Comment by kuni-toko-tachi | Hacker News Reader

People who chose AngularJS are looking more and more foolish everyday.

I wouldn't choose Angular for a new project right now because it's in no man's land: 1.x is dead, 2.x is not available, and there's no path between the two.

That said, Angular gets the job done. It scales better than people think it does (it's inefficient but modern browsers are just so fast it rarely matters) and it's a lot more complete than React. Angular is a full MVC framework while React is just about the V.

> 1.x is dead

What does that even mean? It's very much alive and 1.4 is going to be released this year.

That's like the people who called Perl 5 dead because Perl 6 was announced back in 2000.

Dead over the long term, as it has lost momentum.

Perl 5 is dead in the same way. What programming language would you recommend to someone looking to learn programming?

In 2000, you could make a strong case for Perl.

In 2015, there are a half dozen languages ahead in line.

Anyone new picking up Perl is likely doing it just for a project. Same with angular.

Completely agree with this. You can be really productive with Angular and as long as you avoid the most common pitfalls its more than fast enough, and comes with batteries included and a rich eco-system.

The crazy roadmap to 2.x, and the decisions around 2.x in general just makes it a no-go for new projects at this time.

React has a better chance because it is a micro framework or component or just the V like you mentioned.

Typical evolution of new tech is monolithic to micro, frameworks to components/modules/libraries.

In the end micro frameworks or libraries allow more flexibility to change over time.

Always bet on the micro frameworks and libraries, they can be swapped more easily and typically don't create blocks in overall architecture/design.

React is quite large in terms of lines-of-code. I would refer to it as a mili-framework instead of a micro one :)

I would say that lines of code is not a useful metric. From a developer standpoint, what I care about is how much "surface" a library adds, and in how many places. The React API is relatively small, easy to understand, and confined to a single place - rendering my views.

You mean like Netflix? There's already a comment here mentioning they've used both Ember and Angular internally.

Seriously, what a pointless comment.

Why? It was a very good technology (the best?) at the time, and it remained so for a few years.

I'm very happy I picked it for my projects and I'm also very excited about React, which I would probably choose today.

AngularJS was first released seven years ago. React, barely two.

I had no idea it had been so long! Time surely flies

Reply on news.ycombinator.com