It is way to early to say there isn't a way to port to 2.0. 2.0 doesn't even exist.
Again, the code will not stop working magically just because your code is 5/6 years old.
Again, the code will not stop working magically just because your code is 5/6 years old.
That is not what I sad. What I sad is that with the info we have now it seems there won't ever be a way to port the code to 2.x.
The code of 2.x we saw is completely different from 1.x.
> Again, the code will not stop working magically just because your code is 5/6 years old.
You are right, but "the problem is future proofing. What happens when Facebook releases its Oculus Rift browser and I'm still stuck on Angular 1.2 because of my IE8 support, but only 2.0 exploits the Rift properly? What happens when candidates for jobs stop knowing how to use 1.x? What happens when I have to give this technology to non-FEDs who find themselves confused by the conflicting documentation and version-less community code? (e.g. stack overflow snippets that require 2.x but do not say so)? I've seen these problems with other frameworks outside the front end space (e.g. Spring)."¹
I have been there as well, and I don't want to get there again. At least not willingly.
¹http://www.breck-mckye.com/blog/2014/12/the-state-of-javascr...