there is a long standing problem in Team Fortress 2 where the default FOV is 75, as it was on the console ports of the Orange Box, and it's believed to turn off a lot of new players and enrage regulars because they just don't see things in the periphery that everyone else playing at the maximum FOV of 90 does.
i'd be surprised if there are more users of cachy than bazzite.
what gets missed is that bazzite is, to borrow video game parlance, a mod of fedora's atomic desktops. every piece created to build and maintain the system is on github. it's not rocket science, it's a collection of dockerfiles, rpm specs, config files and github actions workflows. and fedora is not going away any time soon.
it was clearly bad enough for everyone else to decide that they didn't want to put up with him anymore. which is what happens in the real world.
online, everyone considers themselves a public figure. and because we can't seem to get shot of public figures, whether they be rapists, homophobes, or just arseholes, alleged or proven, they believe, logically, you shouldn't be able to be rid of them.
offline, if you have someone who makes your life a misery, you tell them to fuck off.
intel has been making graphics silicon since the 90s, the current discrete graphics effort has been going for at least a decade, and in areas like low power video decode and encode it could be argued intel is class-leading. the concept of the "GPU" is a quarter of a century old. this is an especially poor article, especially for a publication running as long as techcrunch.
and grub is a rotting pile while systemd-boot is a simple boot entry multiplexer that rides off the kernel's capability of being run as an EFI executable, it just happens to live in systemd's tree. not a good example
It's a pretty good example of why people think systemd is bloated and does too much. It's a simple boot entry multiplexer. Does it need to live in systemd's tree?
I'm tired of grub too. That's one of the packages on my shitlist. Currently it is broken on my system, as it has been in the past from time to time. I'm tired of the unreliability and have decided to write my own bootloader instead. It will be simple and bulletproof.
I already laid the basic foundation and have the kernel loading into memory and booting. Next step is to get the memory map and pass that along. It's BIOS only for the moment; EFI support will come later, along with other architectures. (PowerPC is next.)
Because they're not all called coreutils. They've got names like sed, awk, and grep, not systemd-named, systemd-analyze, systemd-networkd, systemd-resolved, systemd-timesyncd. I guess that's a good thing though?
