Hacker News new | ask | show | jobs
by jaybeavers 1232 days ago
Both of those are reasonably met on the Steam Deck today which is running Linux…

Now the Steam Deck has an x64 CPU, but I’m running my heavyweight production Windows apps today on a Macbook Pro M1 running Windows 11 Arm in a VM which in turn is running Windows x64 apps in Windows on Arm’s cpu emulator and its a decent experience.

Really heavy apps like Visual Studio (not Code) and Altium (ee cad) are noticably slower, but run juat fine if I tune the VM for ‘gaming/CAD’ setings which basically allocates 12 GB RAM and 4 arm cores to the Windows VM.

Steam Deck does things differently — they have a sufficiently large Win32 compat layer that they aren’t running Windows in a VM at all. Now They don’t run this api layer on top of a x64 over arm layer, but I dont see why that won’t happen somewhere sometime soon…

Valve/Steam has the ‘runs existing Win32 apps without Windows working really well in production and they have a financial engine (games storefront) which is funding the support and improvement of this layer.

Both Apple and Microsoft (and others) have ‘run x86 apps on arm’ running really well in production today.

If Apple really wanted to run Win32 natively, they could do it without much new engineering investment. If Valve decides that an Arm chip makes more sense than their AMD chip in the Steam Deck, they could do it too.

Maybe some third party disruptor leverages Valve’s work and uses one of the (much better than Win11) Linux shells and creates some hardware like the Mac Mini M2 or the MSFT Arm dev kit, we’d see a real contender for Desktop Linux with full Win32 support on Arm.

The real question to me is does anyone outside of Apple have a current gen Arm CPU/GPU that has the performance? My Surface Pro X with Qualcomm Snapdragon is considerably slower than my Macbook Pro M1 running Windows apps in Coherence mode on Parallels Desktop inside a Windows VM. Parallels works, but I end up burning 6-8gb of ram to windows vm overhead and have the overhead of managing dual OSes to make this frankenstack work…

1 comments

Steam Deck is a Windows emulator ignoring the lessons of Windows emulation on OS/2.

The target platform keeps being Windows x86/x64 in what game developers are concerned.

Since Windows CE days for ARM, the amount of device sales have hardly been spectacular, hence Project Volterra, which isn't taking the world of Windows development by storm in any way.

OS/2 is often cited as an cautionary tale of how enabling software for another OS to run is suicide, but everyone who cites it that way makes the wrong conclusion. As counter points, iBCS2 did wonders for Linux adoption and Windows is doing well with Android+Linux emulation. The Steam Deck is also doing wonders with Windows emulation.

OS/2's main problem was that it was only preinstalled on expensive IBM hardware that almost nobody wanted to buy when cheaper hardware was available from IBM PC clone manufacturers like Compaq. The hardware also used MCA, which was more expensive than ISA thanks to IBM's royalties and it was a pain to configure. Nobody wanted that. That sealed OS/2's fate.

That is not mentioning the horrible marketing campaign for OS/2 Warp that made OS/2 sound like it was related to narcotics.

Anyway, had OS/2 been on all of the IBM PC clones rather than Windows, then history would have selected OS/2 over Windows.

Windows is running Android and Linux on their own Hyper-V instances, hardly much emulation going on besides the hypervisor drivers.

Android on Windows requires Windows 11, is US only and uses Amazon store, hardly a success.

WSL is being a success to drive Windows sales, because as Microsoft learned from Apple's customer base, it turns out many developers only care about having a POSIX environment and couldn't care less to support Linux vendors Additionally it helps selling Windows containers on top of Docker tooling, for the same kind of customers.

That is the target, nothing else.