We had Java services that produced JSON, some that used JSPs, and a variety of others. TDD works in some cases, but if you ever wanted to do manual testing - for example, actually see the UI you were working on with real data - that meant redeploying the server after every change.
Play makes this dramatically faster/easier. TDD is better with Play as well: the plugin support, strong test tools, and sbt's ~test command are amazingly productive.
Re:The Play Framework at LinkedIn
by smrtinsert on Thursday February 21, 2013 @06:18PM
(#5261304)
Personally I rarely test all ui because QUnit verifies all frontend code so long as it meets the json contract.
Regardless, thanks for your post, I'll give Play a go!
Re:The Play Framework at LinkedIn
by chaostheory on Thursday February 21, 2013 @03:28PM
(#5260127)
If I were to guess, it would be configuration, more specifically the myriad number of choices and combinations of it. Spring's strength and weakness is the power of customizing it.
the whole servlets/jsp/jsf thing is dead imo, is that where you guys were losing time?