4 ms·
> if Sun hadn't influenced this I was thinking about this recently in a completely different context. Java itself is actually not a bad language for what it t
by commandlinefan 3y ago
> if Sun hadn't influenced this
I was thinking about this recently in a completely different context. Java itself is actually not a bad language for what it tries to be: an easier to use ("safer") C++. It makes for a better "object oriented C" than C++ or Objective-C did.
Everywhere it really went wrong was when Sun got involved. J2EE, and especially EJB, was a complete waste and continues to create problems to this day - the awful but inescapable Spring "framework" was actually a replacement for the equally awful EJB architecture and creates the same bloat but without the licensing costs.
- jjtheblunt 3y ago> Everywhere it really went wrong was when Sun got involved. Java is a Sun product in the first place; i'm misunderstanding what you mean.
- commandlinefan 3y agoI'm separating James Gosling's creation of the language from everything the rest of the company did with it afterwards (although I guess he was working there at the time so technically he was "Sun", too).
- supportengineer 3y agoMy preferred language is Java. I had to teach myself starting around 1998. But for whatever reason I still haven't learned Spring. I haven't needed it for any of my work.
- Smeevy 3y agoSort of the same here. I've read about Spring and built some toy apps to learn more, but I always found myself asking why I would want something like that in my stack if it could possibly be avoided.