I'm new to Scala and to Play, and I'm considering using them for a new project. I see the development on Play 2 is coming along nicely, although the stable version is still 1.x. And there are substantial differences between the two.
What I'm wondering is, if I start a Play 1.x project now, what options can I take that will ease migration to Play 2 in the future?
Namely:
Countries should promote stability, education and employment opportunities and reduce the drivers of forced migration, including by promoting resilience, thereby enabling individuals to make the choice between staying or migrating.
Lacking a clear strategy determined by business objectives. Cloud sprawl caused by not having a clear understanding of the full scope of cloud environments. Exceeding the planned budget. Security weak points and failures of critical services.
On the migration itself:
In general it shouldn't be too complex, but as @lacy said, it depends on your deadlines and the project itself. If it's a critical project, to be finished before next March 2012, I would go with Play 1.x. If it's a less important project, which could be delayed, and that in any case won't be released before March 2012, try Play 2.0.
I wouldn't even bother using Play2 on project for the moment. It still lacks some features and even if the development is going forward, I would stick with Play 1.2.x. Even if I have to admit it is tempting to try 2.0.
But I would never chose the in between solution, though. Starting in Play 1.2.x and trying to migrate toward 2.0.0. It is called Semantic Versionning. When the major number increases, there is no backward-compatibility. Meaning, you either use play 1.2.x or Play 2.0. Trying to migrate is going to cause you more stress, problems then you want to.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With