Python!
-
I think you're using this meme template backwards - the car should say most people and the text for the directions should be flipped. The car is supposed to be going somewhere it shouldn't, not somewhere it should.
-
There's also Safe C++.
C++ devs would literally do anything before using Rust
-
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.
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 think you're using this meme template backwards - the car should say most people and the text for the directions should be flipped. The car is supposed to be going somewhere it shouldn't, not somewhere it should.
You're absolutely right, and I noticed it as well, but I already had some upvotes. Also, I'm a lazy fuck and didn't want to do another one.
-
C++ devs would literally do anything before using Rust
-
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.
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.
-
There's also Safe C++.
wrote last edited by [email protected]why in God‘s name would you ever use that before rust or swift?
-
why in God‘s name would you ever use that before rust or swift?
Libraries/frameworks written in C++ and Rust is a bad match for wrappers.
-
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.
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.
-
But that would imply that Python is faster than the one in this comic!
Python 3.13
