436
Python! (europe.pub)
submitted 1 year ago by to c/programmer_humor@programming.dev
17 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 1 year ago (3 children)

Eh, Python has a very small slice where I'd consider it the right tool for the job for me. It's for when I want a less awful bash script, but going much bigger than that makes me miss type systems.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 6 points 1 year ago

    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.)

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 1 year ago (1 child)

    Optional type annotations started to enter Python around 3.8, and they have really improved the experience. Even if nothing enforces the annotations, the IDEs can pick them up and show them to you in all the usual places.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 year ago

    I used them heavily, but I still run into issues of guessing what type library functions return or expect me to pass in. Sometimes there was no answer because the authors I guess wanted to be cool and accept any type that kinda fits, or they return either this or that type based on the arguments and now I have to assert which one it is to the type linter. And then I'd still get runtime errors about failed property accesses deep in library code and have to figure out wtf they wanted me to do.

  • permalink
  • fedilink
  • source
  • parent