Fast and painless are not the only criteria. Looking at how america typically kills it's citizens it also clear that it has to look peaceful and respectful. Thats why they put a bag over people getting electrocuted and why they don't just fire a shotgun at your head from a close distance.
That's not how it works. Your body can't detect a lack of oxygen but only build up of CO2. If you replace the air you breath with pure Helium, N2, CO, etc. you will just painlessly black out and die.
If it's pure nitrogen it's as painless as it can get. Make sure there is no O2 in there, get rid of exhaled CO2. Simple. But still, your country should think about death sentences in general. If you think nitrogen is too inhumane just shoot them im the head with a shotgun from a close distance, that too should do the trick.
Looks like LateX is not supported but Markdown is. Single underscore leads to italic text. _some text_ will render as some text. Two underscores will render the text bold in markdown. __example__: example
True and I obviously have no idea what I'm doing. But I'm sure it doesn't matter because I don't know anything about music, don't have absolute pitch and just pressed e f f on an online midi keyboard 🤣
Thank you for taking the time to read it ❤️. I'm currently out of office I'll try to find and fix the typo you mentioned once I'm back, thanks for pointing it out.
❤️ Thank you for taking the time to read it. And thank you so much for pointing that out, you are completely right and I totally didn't think about that while writing the article, probably because negative exponents are pretty rare in computer science (as in milli-bytes, etc.). I'll fix that in a few days. Thanks again for pointing that out.
There is a benefit in using 1000 because it's consistent with all the other 1000 conversions from kg to gramm, km to meter, etc. And you can do it in your head because we use a base 10 number system.
36826639 bytes are 36.826639 MB. But how many MiB? I don't know, I couldn't tell you without a calculator.
The underlying chips certainly are exact powers of two but the drive size you get as a consumer is practically never an exact power of two, that's why it doesn't really make sense to divide by 1024.
The size you provided would be 500107862016 / 1024 / 1024 / 1024 = 465.76174163818359375 GiB
Divided by 1000³ it would be 500.107862016 GB, so both numbers are not "pretty" and would've to be rounded. That's why there is no benefit in using 1024 for storage devices, even SSDs.
So you could say 17.179869184 GB or 16 GiB. Note that those 16 GiB are not rounded and the exact number of bytes for that RAM module. So for memory like caches, RAM, etc. it definitely makes sense to use binary prefixes with 1024 conversion but for storage devices it wouldn't make a difference because you'd have to round anyway.
Thank you for taking the time to read it and your feedback.
Your replies here come off as pretty condescending.
That was definitely never my intention but a lot of people here said something similar. I should probably work on my English (I'm not a native speaker) to phrase things more carefully.
You shouldn't just say "did you read the article" and then "it's in this section of the article"
It never crossed my mind this could be interpreted in a negative way. I tried to gauge if someone read it and still disagreed or if someone didn't read it and disagrees, because those situations are two different things, at least for me. The hint with the sections was also meant as a pointer because I know that most people won't read the entire thing but maybe have 5min on their hand to read the relevant section.
Not really programming horror. Just open source. They did something, are kind enough to make it open, they don't care about commit messages so what?