Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I feel this needs to be said about most frameworks these days...by the time anyone agrees on anything, a new framework will come along and everyone will start praising it as the new holy grail.

I'm so glad I did not follow though with an Angular project about 2 years ago. It would have failed miserably and been difficult if not impossible to manage at this point.



What is your last point exactly? How a new version of Angular would have made your project fail so miserably?

Change is great, it makes awesome things happen. New frameworks are here to give you a choice, you don't have to use all of them. Angular2 will come with a lot of new features and Google said that they will keep working on Angular1 until most of the users switched, what's bad about that?


The fact is, there's always a new tool for the job a year or two down the road, but software needs building today.

I launched a major internal admin a year ago with Angular and it's largely on autopilot because Angular is so darn easy to work with when it comes to building new features, especially in the view layer.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: