4 ms·
Speaking of having to rewrite your entire application, play framework has changed how it interops with DI and a number of other significant details every single
by kazagistar 8y ago
Speaking of having to rewrite your entire application, play framework has changed how it interops with DI and a number of other significant details every single minor release, forcing significant changes to update versions frequently. We were pretty gung ho about it at first, but basically all our engineers have burned out on it and we are going so far as to embrace the relative stability and, dare I say, simplicity of spring-boot.
It's possible that for Scala development it is a fairly good option, and some of the pieces like the typesafe config library are pretty nice, but at this point we consider play to be more like a curse word representing incompatible inflexible garbage.
- vvillena 8y agoThat's because they are not minor releases. Play seems to follow the Scala style version numbering (epoch.major.minor). In any case, I'm with you in that some of the changes between major versions they did were painful, especially if the code was structured in certain ways.