>the GitHub Actions log viewer is the only one that has crashed my browser. Not once. Repeatedly. Reliably.

Well, THIS blog post page reliably eats the CPU on scrolling, and the scrolling is very jerky, despite it has only text and no other visible elements.

Well, you're joking, but the entire RAM industry still lists their chips in Gb (gigaBITS) to avoid confusion.

32 Gb ram chip = 4 GiB of RAM.

That's still wrong and you've solved nothing. 32 Gb = 32 000 000 000 bits = 4 000 000 000 bytes = 4 GB (real SI gigabytes).

If you think 32 Gb are binary gibibits, then you've disagreed with Ethernet (e.g. 2.5 Gb/s), Thunderbolt (e.g. 40 Gb/s), and other communication standards.

That's why I keep hammering on the same point: Creating context-dependent prefixes sows endless confusion. The only way to stop the confusion is to respect the real definitions.

It's not wrong. It's the standard definition for that industry.

Damn you're right. It's double-confusing now.

>Why do we often say 1 kilobyte = 1024 bytes?

Because Windows, and only Windows, shows it this way. It is official and documented: https://devblogs.microsoft.com/oldnewthing/20090611-00/?p=17...

> Explorer is just following existing practice. Everybody (to within experimental error) refers to 1024 bytes as a kilobyte, not a kibibyte. If Explorer were to switch to the term kibibyte, it would merely be showing users information in a form they cannot understand, and for what purpose? So you can feel superior because you know what that term means and other people don’t.

Raymond Chen's blog isn't exactly official documentation, even if it's frequently better than the documentation.

I know the only other software with this kind of error: https://github.com/lsd-rs/lsd/issues/807

> Because Windows, and only Windows

ls does unless you pass --si.

Windows also uses KB as measure unit which does not make sense (it's either kB or KiB)

>Unfortunately Archive.today complies with these attack requests in some situations, but is still usually better than others.

Use Onion version :D

Thanks so much for the tip.

Placing the link for others:

archiveiya74codqgiixo33q62qlrqtkgmcitqx5u2oeqnmn5bpcbiyd.onion

Fingers crossed that it works!

There are SoCs with 64 or 128 MB integrated, and people run reasonably complex stuff on it.

I still have 64 MB VPS (OpenVZ) which I use in production since 2012. It runs DNS, VPN, some logging stuff.

Linux (the kernel) has LOTS of functionality anyone barely use or even know. Without that, there's no tooling around this functionality, no adoption. Not even all TCP socket options (setsockopt) are documented!

Systemd pushed forward proper usage of capabilities, better watchdogs (in a broader sense, as systemd supports all kinds of them), isolation, policies, and so on and so forth. You need it all to efficiently control the daemons, and it's great when it's all available in a single suite.

Because of SystemD, you can't use Linux control groups. On systemd systems, only systemd is allowed to touch control groups. I think they even tried to make the kernel enforce this but they failed, so now it just breaks systemd if you do.

Oh, and there's TWO page zooms btw: the one you activate with +/- (or ctrl + +/-), and another one available with touchpad pitch-to-zoom / touchscreens (you can't use it on desktops without touchpad/touchscreen).

It you know what you're doing and scrupulous enough, you can package the software in a way that it works 25 years later.

https://xcancel.com/ValdikSS/status/1843044963443253678