Because we’re not saying it often enough:
Kudos to the author for going out of their way and writing <i>meticulously detailed step-by-step instructions.</i><p>That README shows a great deal of appreciation for other people’s time, which should be commended.
The problem with each of these tools (Lima etc.) is that it’s still fundamentally a virtual machine under the covers.<p>The great thing for me about WSL (and why IMHO it was worth all the effort they put into it), is that because the kernel process tree is running as a native Windows process tree, I don’t have to pre-allocate memory ahead of time.<p>This is murder on Apple’s RAM-restricted laptops, and kind of rubbish on machines with massive RAM too. Most of the time, most of your memory goes unused. The base model Airs/Pros for example need to have 25-50% of your RAM locked away just to run a Linux container at all - when you already have a fairly anaemic 8GB to begin with that’s pretty dire.
I thought it was
"macOS subsystem, for Linux" and got excited before realising it's the other way around.<p>What do Mac users get out of this? I thought most Linux things work reasonably well already
Is there a Linux Subsystem for MacOS?<p>I know about Darling [1] but don't know about how practical it can be because I'm assuming all proprietary frameworks like the core web framework aren't implemented there.<p>[1] <a href="https://github.com/darlinghq/darling" rel="nofollow">https://github.com/darlinghq/darling</a>
This is also achieved through:<p>1) <a href="https://github.com/lima-vm/lima" rel="nofollow">https://github.com/lima-vm/lima</a>
2) <a href="https://github.com/beringresearch/macpine" rel="nofollow">https://github.com/beringresearch/macpine</a><p>With a nice CLI included.
Anyone else reading the title as the reverse of what it actually is?<p>I thought it's something for running (some parts of) MacOS on Linux. Not the other way round.
I suspect you can get rid of all the post-install steps by just installing it over a serial console in the first place (`-nographic` might even make it all automatic, I dunno). See f.e. <a href="https://www.debian.org/releases/stable/i386/ch05s03.en.html" rel="nofollow">https://www.debian.org/releases/stable/i386/ch05s03.en.html</a> <a href="https://teklager.se/en/knowledge-base/installing-debian-over-serial-console-apu-board/" rel="nofollow">https://teklager.se/en/knowledge-base/installing-debian-over...</a>
You can just use Vagrant for this kind of setup. The benefit of that is you can provision so it is able to run your application and you're able to commit it to git and share it with others. Pretty sure it will have a qemu adapter too if you so choose.
Ha: I appreciate having to give it the stupid backwards name because that's what MS did, but unfortunately it's still a stupid backwards name.
It's a poorly chosen name, same as in "Windows subsystem for Linux".<p>It should be called Linux subsystem for macOS if they really need such kind of combination.
I just don’t see why this is needed.<p>Almost everything on Linux has a homebrew version available.<p>Perhaps it could be helpful for pure development needs. I guess.
It will be a while before we're able to have decent support. This is an interesting initiative to follow: <a href="https://macoscontainers.org/" rel="nofollow">https://macoscontainers.org/</a>
Might be even easier to provide (hopefully trustworthy and safe) `msl.qcow2` Debian images with the installation and `GRUB` modifications already done?
Why reuse the horrible name microsoft uses to describe using a VM?<p>I'm loosing hope for anything tech related these days, just bad and concerning
The WSL naming is terrible and stems from a time where Microsoft was an evil monopoly empire, and used all kind of doublespeak regarding Linux, GPL, etc (see Halloween documents). The name stems from its predecessor, Windows Services For Unix (SFU) [1]. Its bad enough Microsoft kept using the doublespeak naming scheme, please don't copy it.<p>What this is, is Linux compatibility layer (running on MacOS). BSDs have (or used to have) such as well, at least FreeBSD used to.<p>[1] <a href="https://en.m.wikipedia.org/wiki/Windows_Services_for_UNIX" rel="nofollow">https://en.m.wikipedia.org/wiki/Windows_Services_for_UNIX</a>