Marmite crumpets shouldn’t exist!

What other cosmic horrors are you creating in your kitchen‽

You want AI that makes chips that run AI faster and better?

You’ve fallen into its trap!

That’s actually just a silly Star Wars reference. “It’s an older code but it still checks out.”

It’s so fun! I’ve been playing every day for three years now and I’m still addicted having loads of fun with it 😁👍

Oh if I wanted to show off my BS skills I’d post this replay:

https://replay.beatleader.com/?scoreId=20047904

😁

PLEASE! Yes yes yes!

🧞

I just remembered that I made a gif demonstrating how to spin in Beat Saber!

https://imgur.com/gallery/mm1WVW5

Yes! I play on a hard floor wearing socks. I spin all the time! 🕺

In fact, sometimes I slide into position to play! 🤣

Have some more spinning!

https://replay.beatleader.com/?scoreId=19582636

This is another… It’s an older replay but it still checks out:

https://replay.beatleader.com/?scoreId=7668607

Yeah! 2025 year of the Linux desktop (for everyone else; it was 1999 for me 😁)

You asked this question in all seriousness but all I can hear is:

Crickets

Beat Saber is the best! If you use the BeatLeader mod it automatically saves and uploads replays whenever you beat your previous score on any given map.

Here’s my Christmas present to everyone to demonstrate this fantastic ability:

https://replay.beatleader.com/?scoreId=20010657

(Make sure to watch the whole silly thing in all it’s glory or you might miss some of the “special moments” 🤣)

I’m 46 and I play every day 👍

without type safety your code is no longer predictable or maintainable

This sounds like someone who’s never worked on a large Python project with multiple developers. I’ve been doing this for almost two decades and we never encounter bugs because of mismatched types.

For reference, the most common bugs we encounter are related to exception handling. Either the code captured the exception and didn’t do the right thing (whatever that is) in specific situations or it didn’t capture the exception in the right place so it bubbles up waaaaay too high up the chain and we end up with super annoying troubleshooting where it’s difficult to reproduce or difficult to track down.

Also, testing is completely orthogonal to types.

Haha: “A space breaks everything.” Fuck YES! Are you kidding me‽ It’s one of the best features!

Why? Because it’s so easy to see. In other languages you’ve got semicolons which are surprisingly difficult to notice when they’re missing. Depending on the situation (or if you’re just new to programming) you could spend a great deal of time troubleshooting your code only to find out that you’re missing a semicolon. It’s frustrating and it makes you feel stupid which is never a good thing for people who are new programming.

Types are in a different category altogether with seemingly infinite reasons why you’d want a feature-rich, low-level type system and also why you’d want to avoid that.

IMHO, the point of Python is to be a simple language that’s quick to write yet also very powerful and speedy when you need it to be (by taking advantage of modules written in C or better, Rust). If it had a complex type system I think it would significantly lower the value of the language. Just like how when I see an entire code repo using Pydantic and type hints everywhere it makes the code unnecessarily complex (just use type hints where it matters 🙄).

I’m not saying using type hints on everything is a terrible thing… I just think it makes the code harder to read which, IMHO defeats the point of using Python and adds a TON of complexity to the language.

The promise of type hints is that they’ll enable the interpreter to significantly speed up certain things and reduce memory utilization by orders of magnitude at some point in the future. When that happens I’ll definitely be reevaluating the situation but right now there doesn’t seem to be much point.

For reference, I’ve been coding in Python for about 18 years now and I’ve only ever encountered a bug (in production) that would’ve been prevented by type hints once. It was a long time ago, before I knew better and didn’t write unit tests.

These days when I’m working on code that requires type hints (by policy; not actual necessity) it feels like doing situps. Like, do I really need to add a string type hint to a function called, parse_log()? LOL!