Thanks for your insight. I agree with your comment about the trade off between the time it takes to fully learn the framework vs the productivity that you will get. I think that’s true for all frameworks. There’s also Javelin if you need something smaller and quick to pick in Java that is similar to Express.js.
Imo if you’re doing Java, you need some inversion of control framework like Spring of Guava. You can’t avoid it especially for larger projects
what I really hate is that it focuses on configuration & customization over convention. At the same time, it is a strength for certain projects and teams.
> Imo if you’re doing Java, you need some inversion of control framework like Spring of Guava. You can’t avoid it especially for larger projects
I completely disagree. I’ve worked on more than my fair share of Spring projects, and as far as I’m concerned, dependency injection frameworks tend to make projects more complex than they need to be. In some ways I think Spring projects end up being much larger than they need to be because of Spring. Not to mention that it turns compile-time checks into incredibly hard-to-debug runtime checks.
Ive been developing with spring for past 3 years and so far I freaking love it.
Ive gotten quite quick with it so I can do an mvp with auth, logging, microservice patterns really fast.
And when project grows in complexity it is very maintainable.
But if you are not expirienced and don't care about maintainability and want something fast then node& express is a way to go imho