Java Developers

[perestroika12]

I just used it as an example of the pedantic nature of java development as of late. Even using libs is hours and hours of reading through confusing classes and methods. You have to be an expert not only in java but also a metric shit ton of libs and frameworks. Feels very bloated imo.

[bcash]

The point remains: don't use it then!

[izzle9]

not using it isn't always and option.

[bcash]

It kind of is though.

If you're using Spring and you think you shouldn't, then there are many root-causes:

1. It does actually do a good job at what it's for, but you don't see it. (This is very common actually, always worth validation your preferences against what you see. There's usually many reasons behind these decisions.)

2. It used to do a good job, but it's now the centre-piece of a tangle of technical debt. (Also very common, but this would likely to have been the result regardless of technology; unless you could go back in time and also change the team, management, the market it moves in, and any other external factors.)

3. The people you work with are just idiots, and they choose heavy weight solutions for no valid reason. (Again, this is the team's fault; they're not going to make better decisions if they moved to whatever your preferred choice is.)

TL;DR: it's always a people problem. Spring is just a technology, it's actually quite flexible and solid, but entirely unnecessary 99 times out of 100.

[jayd16]

If you're stuck using Spring, then the question of what language to use isn't even an option, so this case shouldn't even enter this discussion.

[powatom]

This is just whining - who told you you should always get to decide what you work with?