Very weird style. Inconsistent heading styles. Four tilde code blocks? That's totally nonstandard. Why?
Yeah unfortunately these numbers don't really allow any conclusions to be drawn at all.
Also they're not really related to supply chain security which is more about deliberate subterfuge. I think the interesting stat there would be how many authors are being trusted typically for each crate.
It's because as soon as one country forces it on their citizens the others can say "it can't be that crazy - Australia and the UK have already done it!"
because someone believed an ANSWER on a different question answered my question
Yeah that is actually their official position. Your question is duplicate if an answer elsewhere might answer it, which is clearly absurd. Essentially they think "what's 1+3?" is a duplicate of "what's 2+2?".
I think fundamentally they gamified moderation too well, and for many people they turned the site into a mod-maxing game, which obviously makes it an abysmal place to be for normal users.
having the data inline
It's not as simple as that, depending on the architecture. Typically they would fetch 64-byte cache lines so your 128 bytes aren't going to be magically more cached than 128 bytes on the heap.
Avoiding allocations may help but also maybe not. This is definitely in "I don't believe it until I see benchmarks" realm. I would be really really surprised if the allocation cost was remotely bad enough to justify the "sorry your file is too long" errors.
Can't remember tbh. It was a work setup. It wasn't an unreasonable one though. 32 is not very many!
I hit a bug recently in KDE Wayland where the task bar was just slightly offset from the edge of the screen, so there was a gap behind it. Very dumb.
OPAM (OCaml's package manager) had a bug where it couldn't find curl or wget to download stuff with (don't ask me why it shelled out to those in the first place) if you were in more than 32 Unix groups. Have fun thinking of a reasonable explanation for that!
22 characters is significantly less useful than 255 characters.
You can still use more than 22 characters; it just switches to the heap.
nothing I am going to store is ever going to require heap allocations
I would put good money that using 256 bytes everywhere is going to be slower overall than just using the heap when you need more than 22 characters. 22 is quite a lot, especially for keys. ThisReallyLongKey is still only 17.
It's just not a very good name. Awkward even without the mpreg/preg thing. Steps on ffmpeg's toes too much. Just pick something unique. Videoh. Muxy. Movrify. Flippityflop, whatever. I thought about those names for literally 10 seconds. You can definitely do better than ffmpreg if you think harder!
I mean, it would be great if this succeeded... ffmpeg is nice and all but its interface is clearly terrible and there's absolutely no way it is remotely secure. Anyone that uses it on a server basically has to run it in its own VM, or a severely locked down sandbox.
But good luck supporting all the codecs people expect. I'm not even talking the obscure ones ffmpeg supports; just the ones "normal" people use will be a life's work.
Also you have to change the name!
Quite well known now because Rust-haters like to point out how they're awkward to use in Rust.