It's really more like Remote Desktop+. It has some additional "features" (slight retch) on top of traditional Remote Desktop features.
Let's wait and see if it's actually more secure than traditional Remote Desktop.
(and I'd still rather use Wine)
Did they invent X11 Forwarding over the network?
Btw. when we get wayland forwarding over Network?
waypipe exists, but it's still not perfect.
Never heard about this. Thx.
Btw. when we get wayland ~~forwarding over Network~~?
/c/foundthenvidiauser
Unlike X11, Wayland was never intended to be network transparent. As others say, solutions like waypipe and more tradionally RDP and VNC exist.
Exactly. We won’t. We’ll get specialized video stream over network. I’m not happy about this regression. I understand that was a willing sacrifice to achieve better local performance, but I’m not sure it was worth it.
Their reasoning was that X11 network transparency had been broken for quite some time. If you tried running chrome, most games, or anything with modern hardware acceleration over X11 forwarding, they wouldn't work.
So, IMHO waypipe is actually an improvement in terms of compatibility, rather than a regression.
You always had the option to send frames over the net using VNC and such. But for many use cases, X over SSH was absolutely fantastic.
I remember using it on a very basic DSL connection to work remotely back in 2005, and it was almost like running local. You don’t get anywhere near the same performance with VNC or RDP.
X11 can render individual windows (Xclients) through the network on another Xserver since decades. With XPRA you can even buffer them, to move them from one Xserver to another or make sure they survive network disconnect. It's very cool, but not widely used.
I thought this was dumb as fuck, but I think I understand what Microsoft is trying to do here.
What might not be obvious is that this "Windows" app is for iOS, Android and Linux - yes, it's a replacement for remote desktop but it's specifically a remote desktop app to connect to Windows machines.
So while I still this this rebranding is entirely unnecessary, I can see that they are trying to clearly distinguish "I'm not on windows and I need to do something on windows so I'll use the windows app for that" .
It also means less confusion when "remote desktop" doesn't let you connect to your Mac or whatever.
One year from now: web search "Windows App broken" and then starting cutting myself.
Something tells me the community forums will still refer to it as remote desktop or RDP anyway
I was like, this has to be fake. https://arstechnica.com/gadgets/2024/09/microsoft-releases-a-new-windows-app-called-windows-app-for-running-windows-apps/
As I understood this is some remote running layer, while WINE is an emulator.
WINE is an emulator.
ಠ_ಠ
Wine Is Nothing but an Emulator
Oh dear cheddar, what does WINE stand for?
WIAE?
so by now even Microsoft acknowledges that it has lost the battle of making computing synonymous with Windows?
FOSS release of Windows when?
FOSS release of Windows when?
Can you imagine if that entire code got released tomorrow, without Microsoft selectively cleaning it up first?
I remember WinXP getting decompiled a while back and people thought it was pretty wild. Can you imagine Win8+?
Bet we'd find a few comments like
#Yes it's a massive security hole but don't ask questions. LOL
I think we'd still be shocked at how much data collection it does. And probably how "I don't know why it works but don't touch it." The code is. (It was written by people, after all)
I've always felt a lot of Windows' "dependability" is really just slick presentation and the mystique of a black box that sounds solid when you knock on it.
But what bothers me so much, as a non-career-coder and DIY-computing learner, is whenever a corporate product breaks, everything is obfuscated with nonsense that is only meant for a company engineer.
At least good FOSS tries to tell you exactly where the issue is.
If Windows went FOSS I bet it would get a lot of human-friendly fixes...and MS would get a lot of new scandals lol.
i read a blog post by a former MS employee who shed some light on the situation. apparently the windows dev team is entirely made up of junior developers. As soon as anybody gets any experience, either MS tries to promote them to management, or they leave to find a better job.
what that means is there is nobody at MS who has deep knowledge of the Windows kernel. So instead of re-writting, re-factoring or making additions, all they know how to do is add things on top of the existing OS.
I don't think this is strictly true. They do tweak parts of the kernel such as the CPU scheduler to deal with new CPU designs that come out which have special scheduling requirements. That's actually happened quite a bit recently with AMD and Intel both offering CPUs with asymmetric processors with big and little cores, different clock speeds, different cache, sometimes even different instructions on different cores. They also added ReFS not long ago, which may have required some kernel work.
I can understand though if they have few experienced people and way more junior devs. It would probably explain a lot to be honest. A lot of Microsoft stuff is bloated and/or unreliable.
HyperV4every1 version whateverthefuckitis
But not all Windows apps can be run via Wine, at least some apps related to some tools I’ve had to use were not available
Let me guess? CLOUD VMS? "Emulation" tries the most generic app: Doesnt work. Office apps will be the only functioning apps.
Sounds awful lot like Citrix...
Yo dawg…
*xibit-meme.jpg*
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.