Hello, I am not certain this is the place to put this issue, but last night I had an interesting thought. Me and my colleagues, we have started a really big project in the last 6-7 months, and we are still in the phase where we can switch versions ... freely ... But switching from now to 2.0 beta is a big commitment. (And doing this down the road is completely out of the question, 2 years of work at the end of if rewritten in 2.0 is a complete unicorn from an economical standpoint).
So I had the following idea, a big project it should have most of its components decoupled, and we could actually use two versions of angular (1.3-1.4 and 2.0b) for different modules. This particularly applies in our case because we have a the base of the project, the infrastructure to say so, and then we have several modules already developed in a alpha-beta stage, now, one of those modules is a mammoth that needs JointJS and a lot black-magic angular 1.4 work, the initial thought of switching that module to 2.0 now I think is ... suicide :). So my idea / question / conversation starter is couldn't we run angular 2.0 or the 1.3-1.4 in a different namespace than the other one ? The infrastructure of the project and the new, more usual modules can be developed in angular 2.0, while the more difficult ones could remain in 1.3-1.4 up until 2.0 is stable enough to make the transition to. In the end, we are trying to develop our modules lile IN > [ ] > OUT, we are not interested what is in the middle as long as the result is what we want. Thanks, Arthur. -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
