this post was submitted on 09 Jul 2023
91 points (100.0% liked)
Technology
37746 readers
554 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That sounds like a horrid decision. Imagine having to troubleshoot a relative's computer, which isn't working because their internet is down, or is too slow to support streaming Windows like that.
It just sounds like a nightmare all-round, both from a Microsoft Standpoint, since they would have to build all the hardware to support it, people who would have to troubleshoot an issue that might show up on either the local or networked version of Windows, but not both, and from a security standpoint, since it seems like it would make it a lot easier to just hijack the whole computer using that kind of mechanism, with the user being none the wiser, for the most part.
Guaranteed this is so they can run even more malicious proprietary software because client side malware scanners are a blocker for “progress”
And in the peak of all irony, they will likely have Linux running the client to stream in all the proprietary dogshit