I’d argue that ‘a bunch of additional code’ to solve for memory safety is exactly what you’re doing in the ‘defining memory safety away’ example with Rust or Swift.
It’s just code you didn’t write and thus likely don’t understand as well.
This can potentially lead to performance and/or control flow issues that get incredibly difficult to debug.
IIRC Nebula has an exclusivity clause in their contract not allowing content creators to upload to other platforms, though I could be thinking of CuriosityStream.
Didn’t know the people behind the mp3 format were into tooling for metalworking. Guess it makes sense, it involves a practical application for use of sound, and they are a research institution.
I wonder if the metal can hear the difference if it’s not the full 192 kHz.
They shine through my windows at night and are truly horrific.
They’re down the entire alleyway behind my place, and a walk to the grocery store at 7pm during the winter makes your body and mind think it’s sunrise.
Adding together all the different standards/feature sets a chip supports and then aggregating the bandwidth into a single number is actually a very reasonable way to arrive at an approximation for total chip computational throughput.
Ultimately, unless the chip architecture is oversubscribed or overloaded (unsure what the right term is), the features are all meant to be used simultaneously and thus the bits being read/written have to come from somewhere.
That somewhere is a % of the total throughput of the chip.
Stated another way — people forget that there’s almost always a single piece of silicon backing the total bandwidth throughput of modern computing devices regardless of what ‘standard’ is being used.
I've taken multiple 10 year old T-Shirts with holes through 10% of them in to the Patagonia store and they've let me walk out with new product off the rack.
I think the author raises a good point about how much human time/energy/effort go into creating content for systems that are at best closed loops when it comes to search-ability/discovery methods, and prone to disappear completely if one company loses funding or has a policy change at worst.
Both of those seem antithetical to the free exchange of information that was the ethos of the early internet.
I also recognize the profound economic incentives that work against that free exchange of information, and I'm not offering a solution, so grain of salt and all that.