Tom’s has had a well known Intel bias since its inception.

Sure, but you’ll get diminishing returns most likely as consumer hardware doesn’t really have the resources to scale that way very well if all the VMs are running demanding apps simultaneously.

Even for something like 4 VMs that just do NVenc, there are limits for how many streams the GPU can do. I think there’s another patch that lets you raise that, but at some point you’ll run out of resources quick. Even powerful consumer gear isn’t really designed to be used by more than one user/app and it starts to show the more you virtualize and split those resources.

That’s the act I was thinking of. I’m almost certain web streamers will say it doesn’t apply to them…..and it’s definitely one of those things you’d take for granted until you hit the “new” streaming medium and realize why it was necessary in the first place.

Reminds me of OS/2

There was a 3000??? I thought it stopped at 2000!

I fired up my copy of Ocarina a couple months ago. To my surprise, all 3 save files were intact and not corrupted! Could not believe it.

Go for a vintage correct OS for a challenge, try Haiku!

It’s astounding. The same reason why the Steamdeck is better than the Asus and Lenovo imitation handhelds is why people will want the Apple Vision Pro compared to building your own headset and PC. Yet just because it’s Apple, all the edgelords are out in force refusing to see why a product combining existing technologies for you is better for the masses than one you cobble together yourself.

Didn’t we do this already back in the 90s with IE bundling??

The most annoying part I think is because I so rarely need them. All my Pis run headless, but the one time I do need direct console access I have to find the bloody adapters. Leaving them attached and unused is just asking them to get damaged.

Rather than using micro-hdmi (which hardly anything uses), stick a pair of usb-c DP ports instead if size is an issue. at least then I don't need adapters that are ONLY needed for the Pi.

Depends on your system. Desktop have different requirements than servers.

On both at minimum, I'd keep /home and /var/log separate. Those usually see the most writes, are least controlled, and so long as they're separate partitions they can fill up accidentally and your system should still remain functional. /tmp and /var/tmp should usually be mounted separately, for similar reasons.

/boot usually keep separate because bootloaders don't always understand the every weird filesystem you might use elsewhere. It would also be the one unencrypted partition you need to boot off of.

On a server, /opt and /srv would usually be separate, usually separate volumes for each directory within those as well, depending how you want to isolate each application/data store location. You could just use quotas; but mounting separately would also allow you to specify different flags, i.e. noexec, nosuid for volumes that should only ever contain data.

/var/lib/docker and other stuff in /var/lib I usually like to keep on separate mounts. i.e. put /var/lib/mysql or other databases on a separate faster disk, use a different file system maybe, and again different mount options. In distant past, you'd mount /var/spool on a different filesystem with more inodes than usual.

Highly secure systems usually require /var/log/audit to be separate, and needs to have enough space guaranteed that it won't ever run out of space and lock the system out due to inability to audit log.

Bottom line is its differnet depending on your requiremtns, but splitting unnecessarily is a good way to waste space and nothing else. Separate only if you need it on a different type of device, different mount options, different size guarantees etc, don't do it for no reason.

Yknow, if that assholes goal was to make SpaceX, X, and rename Tesla to CarX that might actually make sense