Hacker News new | comments | show | ask | jobs | submit login

Even though this is still called "Angular", this new version has barely any resemblance with the previous one, it's really a totally new framework.

It's a bit sad to think that all this knowledge I have of Angular 1 is now obsolete but I'm excited to dive into this new framework. If it's half revolutionary as Angular 1 was, it's going to be a pretty interesting time.




I have to agree. Will there be backwards compatibility? If not, upgrading to angular 2 is going to require so much work and we'll probably end up switching frameworks. This could end up like Python 2 & 3.


It is not an upgrade if your old stuffs stop working. Man, 1.0 used to mean something.


What did 1.0 used to mean? I thought that major version upgrades typically mean that backwards-incompatible API changes have been made.


It used to mean that it is stable and it will carry on working as far as it can to the future major versions or until it is end of line of the product.

So I can understand if Angular 1.0 stopped working on Angular 4.0 or 5.0. Breaking apps just on one major revision number is really a bad way to manage frameworks.


It's what killed Drupal for me (and many others). Frameworks should provide for either a porting tool or backwards compatibility between major versions. Otherwise you alienate the people that trusted your in the first place.


Really? Well when it came to programs, one used to expect that older versions of the files used with that program would themselves be upgraded, or would just work. However, when it comes to languages, the major version number is used to indicate breaking changes.

So where does angular lie on that continuum?


You are probably thinking Python 2 and Python 3. For languages like C#, you can compile C# 1.0 code on C# 6.0 compiler mostly just fine. I bet this applies to C as well.


Hard to compare languages and frameworks in this respect. I think a better comparison is frameworks and operating systems. Imagine every major release of the linux kernel killing backwards compatibility with all older binaries and software written.


I think it is pretty exciting, in a way it is about the migration off the desktop. Over the last year we have transitioned from WPF thick clients to a SOA with a SPA front end using Durandal. Using Durandal along with knockout felt very natural to us. We chose Durandal in a large part because it was written by someone that thought like us and leveraged years of desktop best practices and applied it to what we viewed as the "wild west" that is web development. Glad to see Durandal concepts will be making it into a great project like Angular [0], Hope it is a peaceful revolution.

[0] http://eisenbergeffect.bluespire.com/angular-and-durandal-co...


You just made your "python 2/3" syndrome. This will most probably kill AngularJS.


Yes, I think I will keep the reference to the slides for the case when people state Microsoft is the only company changing their mind about libraries.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: