3 ms·
But which one is a better bet, the one that tries to anticipate all your needs and make you happy (Spring), or the one that only cares for the needs of it's dev
by pius 19y ago
But which one is a better bet, the one that tries to anticipate all your needs and make you happy (Spring), or the one that only cares for the needs of it's developers?
I'm a developer with needs and desires that align with the goals of Rails, so I prefer Rails. In addition, I've got no interest in using Java for developing web applications, so that plays into it as well.
The beautiful truth is that no one is forcing anyone to use any of these projects. I am just happy to be making software at a time where there are so many frameworks and tools whose developers not only make their work available for free, but welcome my contributions if I'd like to put in the time.
- Tichy 19y agoSure, I am not saying one should use the one or the other. I just think it is a major reason many people stick to Java. Essentially, using Ruby on Rails carries the risk that your project might eventually steer into territory outside of 37signals interests, and you get stuck (or have to invest into developing Rails). With java, usually all use cases are covered (except for closures).