Comment by throwawaymaths
Comment by throwawaymaths 14 hours ago
run code anywhere hamstrung by 90s syntax and hidden code indirections
Comment by throwawaymaths 14 hours ago
run code anywhere hamstrung by 90s syntax and hidden code indirections
From what I gather everyone is still stuck on Java 8 so no need to check?
Where do you gather this from? We are a startup, on Java and on 25.
Why didn't you choose something more modern/sensible. go/kotlin/anything else on the planet?
Go is more verbose than Java though, in what way would it be more sensible?
Also, Java's ecosystem is unparalleled (top 3 in size, depending on domain it usually has the best packages (e.g. typical backend-related functionality)), has stellar performance, a huge developer base, best-in-class IDE support, even LLMs understand it exceptionally well (given how widely represented it is in the training corpus, plus has a decent type system) if that's your thing.
For a typical backend system, you really have to have a good reason to choose something else at this point.
I tried to check in on Java recently but got a NullPointerException when using the AbstractSingletonProxyFactoryBean !
I'll never understand people making fun of verbosity. So you really prefer short, ambiguous, opaque and unpronounceable abbreviations? Really?!
For me at least, I find it easier to see the shape of algorithms, control flow, and expressions when the variable names are concise. But this also might be because I have found Go to fit my use-cases and thinking style well, and Go programs tend to follow this naming convention.
For example, if I have a struct `PageEntity` with a field `Id`, and I am iterating over a slice of such IDs, I would prefer using `pid` instead of `pageEntityId` as the variable name. But Java APIs and conventions tend to use these longer names, so I find it takes more thinking to remember the different names instead of quickly seeing the behavior of code at a glance.
Java also tends to have a lot of inheritance which results in these long glued-together names and makes it harder to follow program flow because behaviors get introduced in multiple different places (i.e., it has the opposite of locality of behavior).
But those are just my opinions and experiences! I know many people love Java, and it is a versatile and powerful language.
i haven't. do people still use the "class" keyword?
Haven’t checked in on Java in a while?