You can set your Steam Deck up to stream the PS5 with Chiaki (https://git.sr.ht/~thestr4ng3r/chiaki). Pretty cool feature for when the TV is in use.

Good call. I still have mine from 2022. I payed the 5 bucks to pre-order on the first day. I really just thought I was at least putting money into Linux and showing interest. I wasn’t expecting much but, shocked at how good the Steam Deck actually was. Valve really stepped up and turned a decent handheld (that I would still be using today in the state it was released in), into really well done polished device. The LCD is even getting Wake-on-BT in the next Steam OS 3.7 release. I tried the preview, it works great. In a couple years when the Steam Deck 2 releases, if I’m still playing older titles, I’ll probably just wait for the first sale to buy. You can’t go wrong with a Steam Deck. It’ll change the way you play games.

Exactly. Plus live kernel updates. There is really no reason to reboot. Occasionally I have to shutdown to unplug everything and rearrange my office. Once or twice a year, that’s good enough.

That’s what sleep is for. Just lock Gnome and let the computer sleep in a sensible amount of time. Instant on when you need.

No point. Sleep works great and live updates are flawless.

CPU interrupts. There are timer interrupts that can be used for this. In hibernate, only a tiny fraction of the CPU is changing the transistor states. A transistor only uses power when it changes state; i.e. “off” or Hibernate. Transistor state changes when you cycle the clock on a CPU. Anyways, set the register for the timer interrupt and signal the CPU for Hibernate. The timer circuit is still listening to the clock while the rest of the CPU stops listening to the clock. Each clock cycle you subtract one from the register. When the register reaches zero, the timer interrupt wakes the rest of the CPU. Just like moving your mouse or pressing the power button; they signal an interrupt which wakes the CPU.

You gotta work on your Linux kungfu. chroot has always been around. You can install any distro, any version side by side. Now there is even DistroBox. Also, Apples switch from 680x0 to PowerPC to Intel, (Arm the exception), every time, Apple customers were told to pound sand. Imagine you spent 10 to 20 thousand dollars on hardware and equipment and software, shit adds up (it’s not just buying a Macbook Pro for these artists), just to buy it all again. That’s why Apple has always been called out for this. Windows forced updates are hilarious and have only gotten worse and worse over the years from what I hear. Linux can be updated live with no reboot. All my servers are setup like that and my work dev machine. Even the kernel gets updated live. Obviously Android and their forced data collection apps would be a huge no no for a Linux distro.

I’d say these aren’t just “problems” with the OSes. Problems are something you can fix yourself or find a workaround. You can’t work around Windows update, thousands and thousands of dollars of investment into the Apple eco system down the drain every time Apple switches architectures, or Google’s mandatory spyware apps.

Like, isn’t this a failure of the Wine approach (again: FOSS architecture) to keep up with hardware, more than an actual problem with using a Mac?

Dude, you think this is about 32bit libraries. It’s about way more than that. Apple customers paid money for OSX. Why would anybody think FOSS is responsible for fixing the problem Apple knowingly created and not just one time. Keep in mind, Microsoft solved this problem with their WoW64 translations layer (like WINE, but for 32bit Windows on 64bit Windows). Linux has a couple solutions, chroot or rebuilding and repackaging the binaries. Obviously there could be a 32bit to 64bit translation layer for Linux like Windows but why when you have chroot. Same thing can be done on other Unix-like OSes. Apple should have done this for each architecture change. There was no reason to f over their customers each time. Also, keep in mind, I’m not an Apple user, not ever. So it’s them you have to convince that they, “weren’t screwed over; over and over again”. Seriously this was a joke in the late 90’s. Now it’s just reached bullshit levels. Rosetta was the least Apple could do.

Especially when after digging in sufficiently deeply to understand it, you find that it’s actually a deficiency with Wine, not Apple.

WINE should fix this for Apple? WINE doesn’t fix it for Windows or Linux or any of the BSD’s or any other Unix or Unix-like operating systems out there. None of them. If Apple wants to use WINE as the solution, then maybe Apple should pony up some of the money they made on OSX sales and pay some WINE developers and make WINE a first class citizen in OSX. Valve needs WINE for their OS, they came out of pocket; engineers and money. Apple can do the same. Especially for how much their customers pay. There is no justification for dumping this on FOSS to fix Apple’s mess.

It’s the same with Windows. I worked on minkernel and onekernel. There are a ton of pre-processor directives for different cpu’s and all kinds of hardware pre-processor directives. Even pre-processor directives for different companies. Unused code paths are eliminated during compile time. The pre-processor directives are more of an annoyance for the developers anyways. If you didn’t organize your code, then you get what you deserve.

Naa, I used to be Windows kernel dev for Intel. The backwards compatibility comes from the WoW64 translation layer in 64bit Windows. WSL1 was built off the same framework. WoW64 worked pretty good back then. Apparently there is enough drift now that you’ll get the occasional old game or program that doesn’t translate well under 64bit Windows anymore but, works under WINE. Rare, but still good for a laugh.

We could do the same under Linux, but it just seems pointless for Linux. Linux has chroot. Steam Runtime is based on containers which are based on chroot. Chroot is how we played 32bit games on 64bit Linux distros back before distro maintainers started including 32bit libraries with their 64bit install images.

When distro maintainers started building and shipping 64bit versions, they didn’t include 32bit libraries. You had to make a chroot for a 32bit distro, then symlink those libraries in among your 64bit libraries. Once distro maintainers were confident in the 64bit builds, they added 32bit libraries. In the case of Windows, Microsoft created a translation layer similar to WINE called WoW64 (Windows on Windows64). Apple is the only one who said, fuck you buy new software, to their customers. Rosetta is the first time Apple didn’t tell their customers to go pound sand; probably not by choice.

When the new CosmicDE gets to stable, I’m 100% switching.