this post was submitted on 09 Sep 2023
100 points (100.0% liked)
Technology
37719 readers
116 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
"via Windows Update" - key piece of info missing from the headline "for some reason".
Yeah, I don't see a need for Windows update to do any 3rd party stuff.
Why not? We essentially have this in the Linux world and it’s great. You have a package manager that pulls from your distro’s repositories and it’s filled with all kinds of software, although most drivers come packaged with the kernel. Most stuff is completely plug and play. You end up with one click (or command) software installations for just about everything so you’re not hunting around the internet and downloading installers. Everything you need, including dependencies, gets pulled in and it stays up to date without every app bundling it’s own updater. It’s super convenient.
Because Microsoft manages Windows update, it's not like a package manager in Linux.
I don't want Microsoft telling me when I should update an Epson printer driver.
So you want Epson to provide you with a separately application which runs in the background to tell you when to update? Why split the responsibility?
Because Microsoft has no more business managing Epson applications than Epson does, I dunno, Kensington or Belkin.
It's not like Microsoft would be managing them, just providing the repository. I really fail to see how having N+1 separate application update mechanisms (possibly running in the background) would be better than having a central one. Sure, it's managed by Microsoft but if you have a problem with that I'm not sure what you're doing using Windows in the first place