after six months debugging unstructured, freeform python code from my colleagues, i found java strictness paradisal

Another one sees the light.

As much as I like types, Python at least feels more productive than shoving a bundle of public static exceptions back up the JVMs ass.

@deadlyRants No-one really uses checked exceptions anymore, even in Java.

@AlmondSauce Now all that remains is the verbosity, the shitty type system that's both too rigid for quick changes and too lenient to actually help in a meaningful way, the ergonomics of a sinking oil tanker and all the other crap.

@deadlyRants Verbosity is pretty much solved with Lombok. Type system is far from perfect - it's a late 90s job patched with generics in the mid 2000s - but it's alright. Gives sensible guarantees which is the main thing. Certainly not too lenient to be helpful unless you're using it wrong - way nicer than anything you'll see in Python land.

Java ain't sinking, at least not yet. I'd like it to in a way so long as everyone moved to a sane alternative (Kotlin, sure, Python, no way) but it's enjoyed a bit of a resurgence as of late - the amount of recruiter spam I get for greenfield Java projects is staggering.

@AlmondSauce For me it's just a matter of use cases. Python is an excellent choice for prototypes and quick experimentation. I wouldn't use it for larger projects but in those cases I wouldn't like to use Java either. I don't think it adds enough in return for all the annoyances.

Initially I wrote my thesis implementation on Python. After a while it feels so wrong and rewrote in Scala. It was a true bliss.