Same with staff notation: If you want to communicate music to other people, learning the slightly clunky but universally-known written language is generally the way to go.

It's even weirder given that another of the test cases is essentially "We put parts on the frame (OhMyPi) and it went faster!"

The idea that you'd stop trying to express yourself because you're comparing your own artistic voice to the output of an LLM and somehow seeing it as less valid, or less worthwhile, is just sad.

I don't mean that as an insult, I mean it's genuinely sad for you and for all of us as a species.

That's not really a point against it, it's a great tool and it's a ton of fun, but I wish there was a way to use it that at least kind of sort of mapped back to traditional music notation, especially rhythm notation.

It's wild that right up until Rails got popular, we were writing code that served billions of requests off of homebrewed MVC-ish PHP frankenframeworks.

When all else fails, drummers are the best security anyway: https://loudwire.com/sleeping-drummer-stops-band-trailer-the...

Now that's a fun one to think about. Hitscan attacks are just vectors right? So would there be some perf benefit to doing that initial intersection check with a less-detailed hitbox, then running the higher res animated check if the initial one reports back as "Yeah, this one could potentially intersect"? Or is the check itself expensive enough that it's faster to just run it once at full resolution?

Either way, this stuff is engineering catnip.