Rust is completely correct to be a dick about it as well. Type safety is there for a reason.
You know, I always wondered what the original image looked like, and even trusty Know Your Meme doesn’t show it. It looked like this:
a compile-time error is highly preferable to a run-time error
In bigger projects, you tend to miss type safety really bad, really fast. Rust has it built in, Python can have it bolted on. That’s simply one of the many aspects to consider when choosing your programming language.
But don’t worry about it too much. If one thing’s for sure, it’s that you will regret that choice in any case.
You wouldn’t typecast a car.
What about typecasting to a car?
I may be on the wrong side of history but I can’t see what other role a car could get in the film industry except vehicle.
It works and is a pile of jank - Python
It doesn’t work and is a pile of jank - C++
You violated gods laws with how bad your code is and it still runs (right through the wall) - C
You don’t even need to cast in Python, a reference is a reference.
For our American friends: the Opel Corsa is a car.
For the Brits, it’s a Vauxhall Corsa.
For everyone : it’s a sh’tbox (never again)
And that’s why I don’t use Python for anything more than simple scripts
Hey at least it’s not JavaScript which is perpetually high on crack with Object object
Well, that happens when you don’t override the
toStringmethod. Not worse than Java’s 0xf00cu1 + 1 = “11”.
[] + [] = “”
C when I cast a
char * *to achar * * const: okC when I cast a
char * *to achar * const *: okC when I cast a
char * *to achar const * *: WTFC when I cast a
char * *to achar const * const *: okPlease stop, I have CPTSD.
Python doesn’t have casts and is strongly typed.
Do we need any more proof Python is superior?
(I’m ^joking, ^I ^love ^Rust)
