• 0 posts
  • 19 comments
Joined 2 years ago
Cake day: August 6th, 2024
  • Well, ideally you start new projects writing 100% Kotlin while only adding Kotlin code to older codebases you can’t get rid of. Personally, I don’t like mixing languages anyway and I would stay with Java in Java projects. One reason is the bloat argument you pointed out quite correctly.

  • Kotlin isn’t perfect and it gives the devs quite a lot of freedom. I would argue that if your Kotlin code is messy, that’s on you - but it will still be significantly less prone to failures like NPEs. Unless you opt out of null safety by using the dreaded ?-Operator.

  • People like to use it for AI, data science, machine learning (TensorFlow, PyTorch, Keras, …) and even scientific stuff (SciPy, SymPy, AstroPy). So it seems to be the right tool for some jobs, which is all that matters. Your job may be something entirely different and that’s absolutely fine.

    (And no, I don’t use Python either.)

  • I’m an old fuck and I started to code in the late 80s. Fast forward 30 years, I once had to work at a WeWork. One day, directly outside of my small office space, I swear to god, a fucking hipster kid with a Macbook under his arm practiced skateboard moves. That was the exact moment I started hating working in IT. It’s also what I think every Javascript coder looks and acts like.