same width for all setups

look at the culture and mindset which Windows™ breeds.

grapheneos on a secondhand pixel 5 which was about 280$AUD. though i probably should have gotten a newer model considering the 5 is nearing end of life for GOS

i use a custom kill script with overrides such as dont kill firefox, and properly kill discord. then $mod+shift+q to use the standard kill as a fallback

ESPECIALLY if you have gotten used to a fancy window manager or custom hotkeys… the amount of times i go “mod+q … oh, right… alt+f4”

so is systemd

as much as i like having a jack, i more value running grapheneos on a supported device :/

what language am i reading?

this looks like one is using the SI 1000-based units, instead of the binary 1024-based. im pretty sure du has a --si option.

the B (for bytes) is omitted, so it each is ambiguous to whether its MiB (mebibytes – binary) or MB (megabytes – SI).

i may be wrong on the technicals but u get the jist.

maybe his friend is also a radiologist and sent op a picture of his own head

the great thing about foss projects, is that people fork them! try librewolf!

thats fair. device support is a major downside of GOS. but, remember: its not really the fault of the OS, as it requires a lockable/unlockable bootloader, which only pixel phones provide (at least in terms of mainstream phones). blame the OEMs like samsung

wait really? :/

2024 YEAR OF THE LINUX DESKTOP

it is a dynamically linked library, meaning its not in the compiled binary, but its assumed to already be on the system. as opposed to a statically linked binary. this lowers the file size of the binaries, because most will use the standard library.

edit: this may not be 100% correct, but its the general idea