Re:Introducing Play 2.0
by markokocic on Wednesday September 07, 2011 @11:09AM
(#2969809)
It is not hard to maintain backward compatibility, but why be constrained with it? It is hard to evolve a library or a framework if you have to be always backward compatible.
I'd rather have big disruptive incompatible major release that kinda compatible which may or may not break in production in a subtle ways.
Re:Introducing Play 2.0
by moondowner on Wednesday September 07, 2011 @11:12AM
(#2969825)
Reminds me of Tapestry 3 -> 4 and 4 -> 5. A lot of people made plugins and learnt Tapestry 3 and when 4 came out all of that was for nothing.
Tapestry 5 now is a whole different story, and so far a good one.
This sent shivers down my spine. Is it that hard to maintain backwards compatibility? And you would figure that if they did have to break backwards compatibility, there would be a clear migration path instead of this "Don't worry about upgrading. Just continue to use outdated versions of our software forever." attitude they seem to have. It's almost never a good idea to put yourself in the position to have to maintain two diverging versions of the same software if you can avoid it.