Skip to content

Instantly share code, notes, and snippets.

@teropa

teropa/no_migration_path.md

Last active August 29, 2015 14:08
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save teropa/c104e30d8523ffdfaff7 to your computer and use it in GitHub Desktop.
Save teropa/c104e30d8523ffdfaff7 to your computer and use it in GitHub Desktop.
Download ZIP
Angular 2.0's "No Migration Path": A Story in Three Acts
Raw
no_migration_path.md

Act 1

Igor Minar at ng-europe, October 23:

Once 2.0 is ready, then we’ll figure out what’s the best way to migrate. At this point we’re really trying to create the best 2.0 ever, and once we know what that is, we’ll go back and see what is the best migration path. Because if we run it the other way around, that would constrain what we can do with 2.0.

Act 2

David Iffland, InfoQ, October 27:

The team also indicated that there is no migration path from Angular 1.X to 2.0, though they left the door open for this possibility.

Act 3

Coman Hamilton, JAXenter, October 28:

As InfoQ’s David Iffland comments, the framework will be “drastically different looking”, meaning users will need to get to grips with a new kind of architecture. It’s also been confirmed that there will be no migration path from Angular 1.X to 2.0.

@SekibOmazic
Copy link

Act 4

Don't like Angular? Fine, go use other framework and leave us alone!

@Javarome
Copy link

Javarome commented Nov 3, 2014

Act 3 bis

Igor Minar, Official AngularJS blog-rather-than-some-IT-news-website, October 27:

Once we have an initial version of Angular 2, we'll start to work on a migration path for Angular 1 apps.

@teropa
Copy link
Author

teropa commented Nov 3, 2014

@Javarome Oh, it's even in the blog. Then JAXenter has even less of an excuse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment