In theory Canonical could lock down Ubuntu like that, but it would be the end of Ubuntu. Switching over to Mint or Debian is not a big deal for majority of the linux-users and also Ubuntu would lose all the advantages they can currently pull off from Debian package maintainers. Also I suppose it would bring a ton of headaches with licenses, but IANAL, so don’t quote me on that. And, obviously, that would kill snapcraft too as I don’t see any incentives for developers to support walled gardens for free, so it wouldn’t be all bad.
I’m sceptical with Windows, considering that most programs are installed via EXE files, so the outcry will be huge. But I’m not saying it can’t be a possibility.
With Ubuntu there would only be a chance of it happening if they also make their distro immutable. That way the user could not as easily install packages the traditional way. But even then there might be ways to disable this immutable mode for troubleshooting.
However, this, in my opinion, would cause a mass exodus as Canonical does not have the same advantage as Microsoft or Google have: Windows and android are, to an extent, closed off ecosystems. Thus switching to another system is very hard, as not every software is available on every other system, so potentially subpar alternatives and comparability layers, whose functionality mostly depends on whether the company behind the original system is actively fighting against these tools or not.
Ubuntu on the other hand, is a Linux distro, so you cab make it like Theseus and recreate this distro more or less with the sum of its parts, if need be.
Code signing for EXE is already a thing. And @DFX4509B@lemmy.wtf is right, the same thing is happening there. Restriction are getting more inconvenient, with Microsoft now talking about a maximum code signing certificates validity of 72 hours, with identity verification getting more strict too. Valid code signing certificates are not mandatory yet but I guess it’s a matter of time before we need to type powershell commands to disable restrictions.
Plus Windows already tried blocking sideloading with S Mode. What’s stopping them from permanently enacting that for the Home SKU at some point down the road given their recent track record of implementing unpopular things regardless of public outcry?
Also, what’s stopping Google from just completely rewriting Android as a Windows-style closed-source OS that they have complete control over at some point?
How soon before Windows copies this, given they already tried this sorta lockdown with S Mode?
Also, couldn’t Ubuntu hypothetically lock down the Snap store like this?
In theory Canonical could lock down Ubuntu like that, but it would be the end of Ubuntu. Switching over to Mint or Debian is not a big deal for majority of the linux-users and also Ubuntu would lose all the advantages they can currently pull off from Debian package maintainers. Also I suppose it would bring a ton of headaches with licenses, but IANAL, so don’t quote me on that. And, obviously, that would kill snapcraft too as I don’t see any incentives for developers to support walled gardens for free, so it wouldn’t be all bad.
I’m sceptical with Windows, considering that most programs are installed via EXE files, so the outcry will be huge. But I’m not saying it can’t be a possibility.
With Ubuntu there would only be a chance of it happening if they also make their distro immutable. That way the user could not as easily install packages the traditional way. But even then there might be ways to disable this immutable mode for troubleshooting. However, this, in my opinion, would cause a mass exodus as Canonical does not have the same advantage as Microsoft or Google have: Windows and android are, to an extent, closed off ecosystems. Thus switching to another system is very hard, as not every software is available on every other system, so potentially subpar alternatives and comparability layers, whose functionality mostly depends on whether the company behind the original system is actively fighting against these tools or not. Ubuntu on the other hand, is a Linux distro, so you cab make it like Theseus and recreate this distro more or less with the sum of its parts, if need be.
Code signing for EXE is already a thing. And @DFX4509B@lemmy.wtf is right, the same thing is happening there. Restriction are getting more inconvenient, with Microsoft now talking about a maximum code signing certificates validity of 72 hours, with identity verification getting more strict too. Valid code signing certificates are not mandatory yet but I guess it’s a matter of time before we need to type powershell commands to disable restrictions.
Plus Windows already tried blocking sideloading with S Mode. What’s stopping them from permanently enacting that for the Home SKU at some point down the road given their recent track record of implementing unpopular things regardless of public outcry?
Also, what’s stopping Google from just completely rewriting Android as a Windows-style closed-source OS that they have complete control over at some point?
I used the s mode and i was eating my desk in the meantime.