Re:Scala vs. Node.js as a RESTful back end server (2015)
by dk8996 on Sunday April 24, 2016 @12:05AM
(#11558500)
I have used Play Framework in production and its really good -- I really hope there is more adoption like we have seen with Node or Rails. The only complaint, is that there have been big changes from 2.0 to 2.5. Moreover, the documentation on the site is just OK, examples in the community can be out of date, and books are out of date as well.
[ Parent
| on HN ]
Re:Scala vs. Node.js as a RESTful back end server (2015)
by hhandoko on Sunday April 24, 2016 @04:55AM
(#11559033)
What do you think of upgrading incrementally via each minor versions (e.g. 2.0 -> 2.1 -> 2.2, etc.)? It will be easier to reason (and debug) the changes between each version, and test compatibility on the dependent libraries.
PS. I have a Play 2.3 app already in production, 2.4 currently in development, and plan for a new app on 2.5. I'm upgrading from the oldest one first...
Re:Scala vs. Node.js as a RESTful back end server (2015)
by dk8996 on Monday April 25, 2016 @10:51AM
(#11564526)
Upgrading minor versions is the way to go. It still seemed like a pain to upgrade since Play Framework has changed quite a bit in the 2.X branch -- more than you would think. I am not trying to trash Play Framework since when you get it up and running its simple the best. I'm a big fan of the JVM.