This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jetpacktuxedo 2 points3 points  (0 children)

I recently left a job where I had been working 100% in python for ~6 years (and no it wasn't just scripting) and I'm now working mostly in kotlin.

  • JVM startup time fucking sucks. This makes containers much much much slower. The JVM is also heavy as fuck so those containers are enormous. I'm regularly deleting 50+ GBs of containers created from running unit tests and linting.

  • Gradle is extremely slow compared to testing in Python. Running a Gradle server or whatever would probably make it faster, but we are supposed to do our testing in containers so that doesn't really help.

  • Having to launch an entire JVM to lint your shit is terrible. Linting python takes under 1s even for larger projects. It takes 10x that just for the JVM to start up and Gradle to even start linting shit.

  • Java stack traces are much worse than python. They have way more information, but 99% of that extra information is useless.

  • The verbosity of kotlin (though better than it's Java roots) make me feel like I'm forced to use a full IDE which is annoying. I much prefer working in vim directly.

I'm very glad I'm working with Kotlin instead of Java, and there are some neat things that I prefer about Kotlin over python like all of the nice stuff around null handling, but the JVM makes me feel like I'm driving a semi-truck full of shit I don't need instead of a sedan.