There is a feature of Windows called “Windows Subsystem for Linux (WSL)” already that basically does the inverse of this (windows host, Linux VM).
https://github.com/microsoft/WSL
The feature is a windows subsystem (for running Linux).
/SUBSYSTEM linker switch was used to specify the target subsystem at compile time, enabling applications to be compiled for different environments such as console applications, EFI boot environments, or native system processes.
In this nomenclature, WSL follows the original naming conventions (although SUA should have been called WSUA).
No harm done though. Your comment is worth reading, it would have had its place upper in the tree.
And also, it doesn't really follow that nomenclature. Those all follow "user code target" Subsystem. Windows Subsystem, OS/2 Subsystem, Posix Subsystem, etc.
If you don't want the latter part, you'd be better served with the dockur/windows image + FreeRDP
This project looks like it does that, but I could be wrong.
It's reminiscent of rootless mode in Parallels, just as janky, too.
That's what "rootless" mode does.
My experience with it is that FreeRDP in rootless mode isn't very good for Windows applications that do anything special with window borders. Using Office and many other programs became a pain.
When it worked, it worked really well, though. Reminds me of the same feature that VMWare used to offer many years ago for running XP/Vista programs on Windows 7 through a VM.
if you are capable of running linux, you're capable of working out the various ways to bypass that sign-in "requirement".
I could probably drop my dad in Mint and he’d assume windows just looks different. Maybe that’s a tad facetious but also ehhhh I could maybe get away with it
Half the time it's something like "Plorglewurzle leverages your big data block chain to provide sublinear microservices to Azure Cloud infrastructures"
At least this one kind of shows you having to install Windows.
Must be why I’m not wealthy. I always figured one would have to show people a reason why they should give boat loads of money…
This one hit hard. It turns out Phineas Barnum was right this whole time.
If it's a good thing with substance, they do.
If they don't, don't use it. This usually hints at a broken culture/missing substance. It _can_ also be ineptitude, but that too is not your problem but theirs.
You woke up this morning not having the problem this sets out to solve. You can go to sleep and rest easily this night, knowing that you still don't have whatever problem this sets out to solve.
If you should one day wake up and notice that you have a problem this could solve, you will find yourself googling for a solution, again side-stepping this whole marketing nonsense.
Unfortunately many companies have realized that engineers don't make purchasing decisions. (Mearly suggestions) Rather, C-Suite, who knows nothing about the technical side of things, and everything about the buzzword side, makes the decisions. As a result, companies know that if they just throw a bunch of inflated marketing mumbo-jumbo at the user, while it will turn off every engineer asking "WTF does this actually do and how does it work", some C-Suite will run out and purchase it without asking, then force their entire team to use it because it "produces synergy of the AI block chain and big data cloud APIs while enhancing productivity". Then us Engineers are stuck using it, whether we wanted it or not.
Similar projects exist for gaming for example Looking Glass, which also uses a Windows VM on KVM (the "Windows in Docker" thing is a bit of a lie, Windows doesn't run in the container, Windows runs on KVM on the host kernel).
UX wise, this is similar to RAIL.
That's not to say that this isn't neat, but it's also not something new (we still have two flavours: API simulation/re-implementation and running the OS [windows]). If this was a new, third flavour, that would be quite the news (in-place ABI translation?).