3 ms·

Technically speaking, it's hard for me to take anything away from Java, other than critiquing the object-oriented nature (Kingdom of Nouns) and some of the synt

Technically speaking, it's hard for me to take anything away from Java, other than critiquing the object-oriented nature (Kingdom of Nouns) and some of the syntax. You can certainly build amazing things in Java. That said, sometimes life is just based on a feeling that may not always be perfectly rational. For me, Java feels like it represents a hell of a lot of shitty businesses that I don't want to be associated with. If there's a stereotypical shitty mid-size corporation out there that engages in shitty behavior and manipulates the H1B system and views programmers as fungible cogs and works on the most boring banal shit out there, you know almost without looking at them that they're a Java shop. There's no part of that universe that I want to be a part of. The only thing that made me want to take a half-look at any part of the Java ecosystem for future work is Clojure.

ponkpanda 4y ago
I can't speak for you personally but I think its simpler than that - Java is unfashionable because it's ubiquitous. It's the Ford of programming languages. Not every problem needs a Ferrari - indeed its bad for the organization to be building everything with Ferraris. I do wonder whether someone has looked at the game theory of all this - how devs (and employers) pick langs and frameworks as a strategy to maximize their respective positions under competition. It's also used by some pretty huge and non-middling corporations. I don't know why I'm defending it - I find Java a too verbose and don't use it personally- however if I were employing and needed to build anything that wasn't a game, an OS, embedded etc. I'd go with Java for large chunks of it because I can find good people to build, maintain and improve it - for years to come. I'd probably throw in some Go and perhaps C++ for compute bottlenecks.

ponkpanda 4y ago

I can't speak for you personally but I think its simpler than that - Java is unfashionable because it's ubiquitous. It's the Ford of programming languages. Not every problem needs a Ferrari - indeed its bad for the organization to be building everything with Ferraris. I do wonder whether someone has looked at the game theory of all this - how devs (and employers) pick langs and frameworks as a strategy to maximize their respective positions under competition. It's also used by some pretty huge and non-middling corporations. I don't know why I'm defending it - I find Java a too verbose and don't use it personally- however if I were employing and needed to build anything that wasn't a game, an OS, embedded etc. I'd go with Java for large chunks of it because I can find good people to build, maintain and improve it - for years to come. I'd probably throw in some Go and perhaps C++ for compute bottlenecks.