@islander We're replacing all our Algorithms with Procedures, which are much more ethical
i refuse to give context
java, long
you know, working with java 19 has been surprisingly pleasant - switch expressions and pattern matching eliminate multiple former footguns with the language, and there are at least some language features for dealing with null even if they're not widely used and somewhat clunky
and verbosity is really more so a codebase problem than the language itself (though java doesn't help either)
...but then every so often i run into some design decision that clearly has its roots dug deep in Old Java: like the .clone()
method returning an Object that you have to explicitly cast to the proper type
and i'm just like ah yes this is the language i grew up on
maybe i'll go to bed early and catch up on the ones i missed while finals were a thing tomorrow instead
i write code so bad it wraps back around to being good
second year at ubc studying math/cpsc/ling
ctf with maple bacon