That’s one kind, and Rust’s “ownership” concept does mean there’s built-in compile time checks to prevent dangling pointers or unreachable memory. But there’s also just never de-allocating stuff you allocated even though it’s still reachable. Like you could just make a loop that allocates memory and never stops and that’s a memory leak, or more generally a “resource leak”, if you prefer.

Rust is really good at keeping you from having a reference to something that you think is valid but it turns out it got mutated way down in some class hierarchy and now it’s dead, so you have a null pointer or you double free, or whatever. But it can’t stop the case where your code is technically valid but the resource leak is caused by bad “logic” in your design, if that makes sense.

My dad survived colon cancer but then any further colonoscopy was denied for five years because it was no longer “preventative”.

High res textures (especially normal maps) and higher quality/coverage audio really made game sizes take off. Unreal’s new “Nanite” tech, where models can have literally billions of polygons, actually reduces game size because no normal maps.

Back in the day TCL was used in a few places in Pixar’s Renderman renderer (called PRMan), and in its connection to Maya. You could write little TCL scripts within the Renderman Artist Tools (RAT) that would be evaluated during scene export. I think this still exists in some form inside Tractor, which is their renderfarm management software.

It’s been a long time since I used prman but generally Python has replaced everything as the “glue” language, which honestly makes things a lot easier. VFX and game dev used to have a hundred different scripting languages rolling around.