3 ms·
> The split between package vendor and package maintainer has classically been the primary reason for malware being rare on Linux. It's also one of the reasons
by dec0dedab0de 8y ago
> The split between package vendor and package maintainer has classically been the primary reason for malware being rare on Linux.
It's also one of the reasons users and proprietary software have been rare on Linux.
It may be why proprietary software is lagging, but I think most users prefer an OS level package manager. They just didn't know about them until the Appstore.
- AnIdiotOnTheNet 8y agoWhich is why everyone loves the Windows Appstore and uses it exclusively. The Appstore works on phones and tablets because they are primarily consumption-only devices, and because users are not given any other choice (also, the installer/uninstaller model has a lot of its own suck). I don't know about you, but that's not what I want out of personal computing.
- TingPing 8y agoMost complaints about the appstore revolve around things like it being slow, clunky, failing to work, being designed around DRM, forbidding win32 early on, etc. Nobody is complaining that applications are in a central location.
- blacksmith_tb 8y agoI am assuming that's sarcasm when it comes to Win10, but 'exclusively using the app store' comes closer to the truth for non-dev macOS users, at least that's my impression.
- digi_owl 8y agoIMO proprietary lags way more because you do not know if your chosen framework (unless it is Qt, heh) will function 5-10 years down the line with minimal investment in updates. The Linux kernel is everywhere thanks to Torvalds (overly late in the opinions of some BSD devs) declaring the API/ABI sacrosanct, and holding the other kernel developers to that (much to the chagrin of some that want to do hail mary changes for sake of security or ego). But the userspace above had been reimplemented again and again because the various libs and such are fundamentally unstable. In far too many cases you can even do a x.y.z+1 update without getting some kind of breakage. Often because someone decided that spec adherence was more important than real life stability, and thus pushed a patch through that altered the API behavior to be more in line with a spec that nobody had complained about for a decade or more.