> Java, as a language is fine I guess, but the culture around it sucks.
Culture is what you want it to be.
There are indeed some ridiculous subcultures within the world of developers who use Java. Like J2EE-anything or any of the baroque frameworks.
It is important to realize none of that is part of Java and none of that is required unless you really want to.
You can use Java simply as a memory safe language with reasonably good type safety that can create wicked fast code and has huge library and tooling support. On all those checkboxes, there are few-to-none options that are so good across all those aspects at once.
Unfortunately so many people just complain about writing TaskStubConsumerWatcherVisitorServiceContainerListIdentifier classes, without realizing nobody is forcing you to do that. So don't.
Culture is what you want it to be.
There are indeed some ridiculous subcultures within the world of developers who use Java. Like J2EE-anything or any of the baroque frameworks.
It is important to realize none of that is part of Java and none of that is required unless you really want to.
You can use Java simply as a memory safe language with reasonably good type safety that can create wicked fast code and has huge library and tooling support. On all those checkboxes, there are few-to-none options that are so good across all those aspects at once.
Unfortunately so many people just complain about writing TaskStubConsumerWatcherVisitorServiceContainerListIdentifier classes, without realizing nobody is forcing you to do that. So don't.