Hacker News new | ask | show | jobs
by dwaite 1281 days ago
Depends a lot on what you are trying to accomplish.

The inability to get something akin to VT220 terminal access and shell scripts on a POSIX-based system without resorting to a virtual machine (a la WSL2) is a deal-breaker for me. The steps for using scripting languages (e.g. Node, Python, Ruby) is typically entirely different on Windows than it is from all other server and desktop platforms.

For those who can spend their time nearly 100% inside an Electron-based or Java-based IDE however, it matters a lot less whether that IDE is running Windows, MacOS or Linux.

> On Windows, x86 and x64 Linux Docker containers run in process isolation at full speed, unlike on Macs where there is CPU emulation required.

You do realize they didn't require us to all burn our old Intel-based Macintosh computers, right? Apple even still sells Intel-based Macs.

Windows requires emulation to run aarch64-based containers. Except on Windows for ARM of course, where presumably they run full speed but those x86/x64 containers above require CPU emulation.

1 comments

WSL2 is not a virtual machine, it's a subsystem. It's basically the opposite of WINE.

You can run all of your favourite languages nearly identically to Linux on Windows either via Docker or WSL2.

> Windows requires emulation to run aarch64-based containers. Except on Windows for ARM

Making Windows and Linux the only platforms with ongoing support for both ARM and Intel CPUs, unlike MacOS where Intel support will eventually expire.

Technically, WSL version 2 _is_ a VM based technology:

"WSL 2 ... uses the latest and greatest in virtualization technology run a Linux kernel inside of a lightweight utility virtual machine (VM)."

https://learn.microsoft.com/en-us/windows/wsl/compare-versio...

WSL1 is not a VM design, but that design reached its limits.

A VM doesn't make it bad - I don't do a lot with WSL but I like it a lot. It's not slow or limited.