583
What's some really unpopular opinion you have?
(self.asklemmy)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Aug 2023
583 points (94.6% liked)
Asklemmy
43945 readers
461 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
Oh, I totally forgot about the chaos surrounding bits and bytes. Personally, I don’t really care which one we use, as long as its unified. Mixing and matching Mb/s for transfer and MiB for storage is truly infuriating. Yes, even the prefixes need to be unified.
I don’t make programs in low level languages, such as assembly, so I don’t really see the benefit of using base 1024 prefixes. If anyone here can convince me why non-binary prefixes are great, I’m listening. As far as I’m concerned, prefixes should be based on 1000, just like in SI.
Having 8 bits in a byte is just another historical relic, and I see no reason to keep it. Systems have changed many times since the adoption of that term, and back in the early days a single character of text took exactly 8 bits. I guess that was important at the time, but why would it be today? Programmers out there can tell us why we need to have two units for data.