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

  • Select an option

    Learn more about clone URLs
  • Save teropa/c104e30d8523ffdfaff7 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save teropa/c104e30d8523ffdfaff7 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. teropa revised this gist Nov 2, 2014. 1 changed file with 6 additions and 5 deletions.
    11 changes: 6 additions & 5 deletions no_migration_path.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,17 +1,18 @@
    # Act 1

    > 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.
    [Igor Minar at ng-europe, October 23](https://www.youtube.com/watch?v=g-x1QKriY90a):

    [Igor Minar at ng-europe, October 23](https://www.youtube.com/watch?v=g-x1QKriY90a)
    > 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

    > 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.
    [David Iffland, InfoQ, October 27](http://www.infoq.com/news/2014/10/angular-2-atscript):

    [David Iffland, InfoQ, October 27](http://www.infoq.com/news/2014/10/angular-2-atscript)
    > 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](http://jaxenter.com/angular-2-0-112094.html):

    > 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*.
    [Coman Hamilton, JAXenter, October 28](http://jaxenter.com/angular-2-0-112094.html)
  2. teropa revised this gist Nov 2, 2014. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion no_migration_path.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,6 +1,6 @@
    # Act 1

    > 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 constraint what we can do with 2.0.
    > 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.
    [Igor Minar at ng-europe, October 23](https://www.youtube.com/watch?v=g-x1QKriY90a)

  3. teropa created this gist Nov 2, 2014.
    17 changes: 17 additions & 0 deletions no_migration_path.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,17 @@
    # Act 1

    > 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 constraint what we can do with 2.0.
    [Igor Minar at ng-europe, October 23](https://www.youtube.com/watch?v=g-x1QKriY90a)

    # Act 2

    > 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.
    [David Iffland, InfoQ, October 27](http://www.infoq.com/news/2014/10/angular-2-atscript)

    # Act 3

    > 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*.
    [Coman Hamilton, JAXenter, October 28](http://jaxenter.com/angular-2-0-112094.html)