Every single non-rust person in multimedia who has done rust has a bitter distaste of the language, including myself.
Just throwing this out there.
@lynne do you think it's more that the generics-and-abstractions style of the stdlib and idiom is a far throw from the way media code is usually written, a question of needing concise "I know what I'm doing" over robustness to changes (because codecs are relatively stable targets), or something else that makes it frustrating compared to C?
@migratory Definitely "I know what I'm doing". 1000%.
"I'm adding a 64bit uint to a 16bit uint, I know what I'm doing, this will never ever overflow, its just what my bitstream reader outputs and I'm reading 8 unsigned bits."
"I know I'm giving two 512x512 partitions of a frame to 2 different threads, I know what I'm doing, those 2 will never ever ever overread/overwrite."
"I just want to quickly hack this overloaded 32bit uint type and add something to it, I know what I'm doing, let me do it".
@migratory That last one was infuriating. Someone had "fun" designing this foolproof abstraction where you could initialize a 32bit uint once, and you could add to it, but if you multiplied it even once it got transformed into another type where you couldn't add anything, just multiply, and if you did it once more you'd end up with something immutable.
I _know_ what I'm doing, let me quickly add something to the "immutable" value. A developer screamed at me for wanting to hack this for a test.
A Mastodon instance for people interested in multimedia, codecs, assembly, SIMD, and the occasional weeb stuff.