PupBiru

joined 1 year ago
[–] PupBiru@kbin.social 1 points 11 months ago (2 children)

i didn’t downvote you, and i went to school before a bunch of things but technology evolves and either we evolve with it or we end up being just straight up wrong in a modern context

[–] PupBiru@kbin.social 5 points 11 months ago* (last edited 11 months ago)

not exactly because of pairs unless you’re talking about 1 and 0 being a pair… it’s because the maximum number you can count in binary doubles with each additional bit you add:

with 1 bit, you can either have 0 or 1… which is, unsurprisingly perhaps, 0 and 1 respectively - 2 numbers

with 2 bits you can have 00, 01, 10, 11… which is 0, 1, 2, 3 - 4 numbers

with 3 bits you can have 000, 001, 010, 011, 100, 101, 110, 111… which is 0 to 7- 8 numbers

so you see the pattern: add a bit, double the number you can count to… this is the “2 to the power of” that you might see: with 8 bits (a byte) you can count from 0 to 255 - that’s 2 (because binary has 2 possible states per digit) to the power of 8 (because 8 digits); 8^2

the same is true of decimal, but instead of to the 2 to the power, it’s 10 to the power: with each additional digit, you can count 10 x as many numbers - 0-9 for 1 digit, 00-99 for 2 digits, 000-999 for 3 digits - 10^1, 10^2, 10^3 respectively

and that’s the reason we use hexadecimal sometimes too! we group bits into groups of 8 and call it a byte… hexadecimal is base 16, so nicely lets us represent a byte with just 2 characters - 16^2 = 256 = 2^8

[–] PupBiru@kbin.social 4 points 11 months ago (1 children)

which is why we have kibi, mebi, gibi, etc

[–] PupBiru@kbin.social 3 points 11 months ago* (last edited 11 months ago) (20 children)

kilobyte (KB) is 1000, kibibyte (KiB) is 1024

at least according the the IEC, and id tend to go with them… SI units say that kilo means 1000

[–] PupBiru@kbin.social 3 points 11 months ago (1 children)

kinda the same reason people suggest something like linux mint over slackware, gentoo, arch, etc… mint is easy to install and is preconfigured to be an easy to use user desktop environment. you can configure any other option to be have like that, but they tend to be a bit more “DIY”, which is great if you know what you’re doing!

dedicated NAS OSes will have good software out of the box that make it easy to configure and manage various common disk-related configurations (RAID, SMB, NFS, etc). you can certainly do all this yourself, but it might not have a pretty, unified user interface, or you might have to deal with software that isn’t compatible with some version of a library that’s in your distro of choice… all resolvable things, but they take time to solve: anywhere from installing a package manually to applying a kernel patch and recompiling the kernel to get something to work

[–] PupBiru@kbin.social 5 points 11 months ago (1 children)

i’d avoid BIOS-based RAID… it doesn’t really offer many benefits over linux-based raid like MDADM, and MDADM offers a LOT of up-sides for portability, repairability, diagnostics, etc

[–] PupBiru@kbin.social 13 points 11 months ago (2 children)

let’s not go too far though… the holders of h264/h265 did put a lot of money and effort into developing the codec: a new actual thing… they are not patent trolls, who by definition produce nothing new other than legal mess

[–] PupBiru@kbin.social 0 points 1 year ago (2 children)

if you interact with them, you’re “using” threads