Play is really not a large amount of code though and it's all in one source tree. It generally doesn't have a lot of "layers" compared to even something like Tomcat; the stack just doesn't get as deep. I've had an easy time digging in to the Play source code when needed.
Just one experience fwiw. Sure, it's still a framework.
Re:Why I'm Moving Away from the Play Framework
by benmccann on Friday March 09, 2012 @01:50PM
(#3685400)
Agreed. I fixed a handful of bugs in Play 2 while it was still young and immature and didn't have much difficulty tracking them down despite not knowing any Scala.
Re:Why I'm Moving Away from the Play Framework
by codemonkeyland on Friday March 09, 2012 @03:48PM
(#3685862)
Despite the propaganda Scala's pretty easy to read.
Re:Why I'm Moving Away from the Play Framework
by fauigerzigerk on Friday March 09, 2012 @02:46PM
(#3685615)
I just fail to see much in these frameworks that isn't either trivial or unnecessary or both. But I didn't mean to single out Play by any means.
But the disparity between what web frameworks actually do for me in any particular application and the amount of layers and dependencies they introduce boggles my mind.
[Edit] If you use maven try mvn dependency:tree