Maybe 8 years ago. Other than Oracle itself the language, the libraries and the culture has changed rather substantially over the last few years.
> Instead of writing programs in a pragmatic way, Java devs feel the need to forcefully over architecture code bases, because there are afraid that a colleague looking at their code will not find it JEEish enough.
Much of the over-design in older Java has to do with ancient methodologies of writing massive specs and having review committees. It has nothing to do with not being JEEish or whatever abuse of keywords you want to make.
> Obviously Go doesn't have the same culture...
Actually I'm starting to see many many Java programmers use golang because many Java programmers are system-like programmers (middleware or whatever its called these days). I guess their behaviors will magical change right?
> So it's easier to hack something quickly with a bunch of functions and variables, like in most dynamic languages.
Well that is true but writing classes in Java is not exactly hard. If it helps you can think of the classes as modules or just files you put your code in. You don't have to write OOP in Java and some would argue most of Java is not OOP.
Maybe 8 years ago. Other than Oracle itself the language, the libraries and the culture has changed rather substantially over the last few years.
> Instead of writing programs in a pragmatic way, Java devs feel the need to forcefully over architecture code bases, because there are afraid that a colleague looking at their code will not find it JEEish enough.
Much of the over-design in older Java has to do with ancient methodologies of writing massive specs and having review committees. It has nothing to do with not being JEEish or whatever abuse of keywords you want to make.
> Obviously Go doesn't have the same culture...
Actually I'm starting to see many many Java programmers use golang because many Java programmers are system-like programmers (middleware or whatever its called these days). I guess their behaviors will magical change right?
> So it's easier to hack something quickly with a bunch of functions and variables, like in most dynamic languages.
Well that is true but writing classes in Java is not exactly hard. If it helps you can think of the classes as modules or just files you put your code in. You don't have to write OOP in Java and some would argue most of Java is not OOP.