Nothing. Rails, PHP, and all Python frameworks can provide you with a productive environment that will work well and scalable. The Spring structure is very mature, and the learning curve is a little steeper - I believe that in one of its main samples there are 55+ jar files. Any experienced programmer will tell you that at some point you will spend some time with each of them if you create a non-trivial web application.
What Spring buys you, as a rule, is a rather complicated structure for creating enterprise applications, for example. when you work with distributed systems and need to handle complex communications between applications.
So, a compromise within the framework is support for functionality and ease of use. There is no a priori evidence or justification for any superiority in a career, and good developers usually work in any of them.
source share