I take my shitposts very seriously.
Realistically, is that a factor for a Microsoft-sized company, though? I’d be shocked if they only had a single layer of redundancy. Whatever they store is probably replicated between high-availability hosts and datacenters several times, to the point where losing an entire RAID array (or whatever media redundancy scheme they use) is just a small inconvenience.
This is not meant for human beings. A creature that needs over 140 TB of storage in a single device can definitely afford to run them in some distributed redundancy scheme with hot swaps and just shred failed units. We know they’re not worried about being wasteful.
Something about child processes, maybe?
I’ve had good experiences with Rustdesk. The client is open-source and the no-cost server components (ID and Relay servers) are self-hostable. The remote server works on X11 and Windows. I use this script to run XFCE+Rustdesk in a headless session:
export SERVERNUM=69
export SCREEN_SIZE='-screen 0 2560x1440x24'
export DISPLAY=":${SERVERNUM}"
export XDG_SESSION_TYPE=x11
xvfb-run --server-num="${SERVERNUM}" --server-args "${SCREEN_SIZE}" startxfce4 & disown
sleep 1
flatpak run com.rustdesk.RustDesk & disown
Sunshine + Moonlight is also a good choice. I have Sunshine installed on a box at home and use Tailscale to connect to it from the Moonlight client. At 1440p 60 FPS it has no visible compression artifacts and responsive enough for gaming.
Even HDR is still “beta” on KDE iirc.
That’s a weird comparison because HDR is never going to happen on X.org (nor probably in the X11 protocol or clients). Wayland is being actively developed and the developers took it from something that can be made to work with some effort and some concessions to something that will reliably work in most cases. The year isn’t 1987 – software isn’t being written by nerds for nerds who can tinker and fix issues or add new features as a patchwork of unmaintainable code.
My home PC, about once a week, or whenever I have to install new software. My work PC, about once a month because the nvidia driver takes fucking ages to update because of DKMS.
As for the servers under my professional care… it depends. Most of the servers that I made run Debian that I update three times a year whenever the downtime is acceptable for the university (spring break, late summer, early december) or if a CVE needs fixing (e.g. xz-utils). One internet-facing server that I inherited still runs Ubuntu 16.04 because some teachers can’t possibly live without some legacy software and will throw a tantrum if upgrading is even mentioned – that one gets zero updates, and I got the dean’s promise in writing that I wouldn’t be held responsible for it.
The big virtualization server still runs ESXi 6 because the university didn’t want to pay for a lifetime license when it was available, doesn’t want to pay for a subscription now, and doesn’t want the downtime required to fully migrate to Proxmox VE. So it gets no updates. Plus it has a bad SSL cert and I need Chromium’s thisisunsafe to bypass the error.
It’s fucking rough out here.
Wayland has an actual future. It is being actively developed. Issues are being fixed and new features are added at least somewhat frequently. X11 might survive past the heat death of the universe, but it will be a stale, fossilized codebase maintained entirely by a small group of opinionated people.
My work PC has a 3080 and the latest nvidia-dkms in the Arch repo. I haven’t had a single display-related issue for probably a year.
Look up where the word comes from if you want to be unreasonably angry.
This same image was posted 16 hours ago.
Unless this is some kind of meta-meme that draws parallels with repetitively using the same commands in CLI.
That is the same kind of pedantry as claiming that ketchup is a smoothie because the tomato is a fruit.
Why do hikers travel to different mountains to conquer?
Neovim with Nvchad is what finally made me ditch pretty much all other IDEs. As much as I used to like Jetbrains, they’ve pivoted to vibe coding so hard that I can’t justify using their IDEs.
Truth, my ass. I’ve read your recent comments. You’re just being a self-righteous dickhead with a false sense of superiority. You derive your self-worth from being a contrarian.
You should also look at which processes use the largest amount of memory. ZFS is weird and might allocate its cache memory as “used” instead of “cached”. See here to set its limits: https://forum.proxmox.com/threads/limit-zfs-memory.140803/
The most useful is probably cat /proc/meminfo. The first couple of lines tell you everything you need to know.
MemTotal is the total useful memory.MemFree is how much memory is not used by anything.Cached is memory used by various caches, MemAvailable is how much memory can be allocated, i.e. MemFree + Cached.
Better not look at the microcode running on your CPU at a higher privilege level than the kernel, then.