81–90 of 473 posts
That seems like a very complex architecture. RDP client and server? That seems like a strange approach for a single machine solution.
Ironic statement considering how X was designed to work.
This can never be the best GNU/Linux experience because you leave up your freedom and privacy at the door of the Windows login. Anyone who is serious about the future of openess, freedom and privacy rights in software and general should strive for the original. I advocate not to hand over MS the control over the Linux desktop.
I don't want to want this, but I do. Only semi-related but what I really want is for easy windows apps on linux that work without fail. I prefer my linux box and generally hate the windows ui (don't get me started on windows settings or audio). I've tried switching to linux full-time but I don't know if I can hack it. Games are 90% there and I can do without the few that don't work with proton, but there are just too…
Which apps? Not that it makes a difference for this conversation, but I'm interested in keeping up to date with what the "killer apps" are that keep people from switching.
>> Weston is the Wayland project reference compositor and the heart of WSLg. For WSLg, we've extended the existing RDP backend of libweston to teach it how to remote applications rather than monitor/desktop. We've also added various functionality to it, such as support for multi-monitor, cut/paste, audio in/out, etc... Did they push those changes upstream? This seems like it could be another way to run GUI apps in co…
I guess getting the right thing for the wrong reasons is better than not getting them at all? I'm not a very good pragmatist.
Earlier quoted context omitted.
It's because WSL2 abandoned the initial goals of WSL1 and just did a VM instead. I wish MS continued evolving WSL1 instead of doing the VM approach but c'est la vie.
The amount of effort that went into WSL1 including the number of bug-for-bug changes involved was tremendous. It blew my mind when WSL2 was announced because the hyper visor approach was already possible (and in use) before WSL1 was announced but MS made an explicit decision to do the extra work to make their own Linux subsystem for Windows the harder/better way… then gave up.
I now have to deal with the fact that every so often the WSL 2 VM will simply consume too much memory, which really stinks.
WSL1 felt SO close to being perfect.
I don't want to want this, but I do. Only semi-related but what I really want is for easy windows apps on linux that work without fail. I prefer my linux box and generally hate the windows ui (don't get me started on windows settings or audio). I've tried switching to linux full-time but I don't know if I can hack it. Games are 90% there and I can do without the few that don't work with proton, but there are just too…
I'll bite - what's wrong with the audio? Friends on mine in game dev often complain Linux audio is hopeless to work with.
Earlier quoted context omitted.
It's because WSL2 abandoned the initial goals of WSL1 and just did a VM instead. I wish MS continued evolving WSL1 instead of doing the VM approach but c'est la vie.
>I wish MS continued evolving WSL1 I do too but only from a techy POV. I think it was awesome they expanded their old posix apis into a drop in linux replacement and wish it could have continued being expanded.
WSL2 is certainly the way to go if you want a more "true" linux experience. I just lament the fact that WSL1 came so close to being true enough.
Extend. > Weston is the Wayland project reference compositor and the heart of WSLg. For WSLg, we've EXTENDED the existing RDP backend of libweston to teach it how to remote applications rather than monitor/desktop. It has been admitted.
And the code seems available on their weston-mirror. It just a merge away.
Microsoft does enough shady things in the now, let us not try not force some EEE pattern.
Earlier quoted context omitted.
Actually, not quite. Wine is closer to what WSL1 was. The closest equivalent to "Windows Subsystem for Linux GUI" on WSL2 for Linux would just be ... running Windows in a VM, with FreeRDP doing per-app tunneling to the Linux host. I think there's even some software for automating this somewhere out there.
>Wine is closer to what WSL1 was Not quite. Wine just translates windows syscalls to linux ones but WSL actually reimplemented the linux api inside the NT kernel (which was designed with the ability to use multiple OS apis.)