> We will no longer distribute source code for the entirety of the Solaris operating system in real-time
In the case of Open Solaris, the code never came out from that point onwards. For Android, the likely end goal is to do the bare minimum of distributing only copyleft code that they don't own copyright to. Until those get replaced with a closed alternative.
Code is turned proprietary by huge corporate with massive development resources. No one could have predicted this.
I'm trying to think of a mobile OS feature addition that has made me say "I need to upgrade my phone" and it just hasn't happened recently. It's more like, damn it, the dastardly thing stopped receiving security updates and now I have to replace it for no good reason.
Isn't Android done yet? What further development is required that couldn't be done by the community?
Yet people ignore him and then realize that was one of those too late types
I suppose lineageOS is the closest thing for Android tho from what I understand it is built upon AOSP
There are quite a few AOSP forks, like LineageOS and GrapheneOS to cite the most famous ones, but with this change in process by Google, they will have to wait a year of no changes, then scramble when the next release of Android drops.
So yeah, if open source orgs can keep going, there's no reason to think government can't do the same. It's about public goods.
If they were to stop, the demand for someone to do it would still be there, and that demand wouldn't be getting met anymore, which creates the incentive for others to do it.
Meanwhile the point is that most of "it" doesn't actually need to be done anyway. You don't need to do everything Google is currently doing. Adding support for new hardware is important, but that has an obvious source of someone to do it because the hardware vendors want their new hardware to be widely supported so they can sell more of it. So all you really need is security updates, and a community can handle that as evidenced by the many instances of it actually happening for other code.
What stops the thing that makes Debian work from making this work?
He usually is, no matter how many times people write him off.
Sure, but in reality they have a legal monopoly on the use of violence, which is a very big deal and makes them qualitatively different from any other collective of people.
You're right, if Google steps away from Android completely then there would be incentive for others to do it, another megacorp will step in. Maybe Facebook or Microsoft or Samsung.
Meanwhile there are hardly any devices that come with it, because Macs come with macOS and Microsoft exerts pressure on PC OEMs, so all of the people running it are people who explicitly did want Debian over anything else, as opposed to many millions of Windows users who have no real preference or an active dislike of their operating system but got it by default with the hardware and may not even realize that anything else is available.
If Google stopped developing Android, it would still be one of the two major incumbent platforms and people would continue to use it. It might even get better because third party apps would have to stop depending on proprietary Google APIs/services and then the community could strip out the Google spying code without worrying about losing access to those APIs. So then the question isn't how to get a critical mass of users -- that's already there -- you just need basic maintenance of a stable code base, which is a thing the community can demonstrably do.
Anyway in the world we both live in, if Google abandoned Android then most people would instantly switch to a megacorp fork of Android with that megacorp's own proprietary APIs and services because people will follow the proprietary things they care about like for eg fast & battery-efficient centralized notifications, an out-of-the-box app store with popular apps like Instagram, and tap to pay.
But I didn't have to explain this to you, you already know this. You know this because "millions of people" is derived from you knowing that the peak Linux desktop marketshare is like 4% out of billions of people. You know this because you said users are "worrying about losing access to those [proprietary, spying] APIs" which is why megacorps who provide these proprietary spying APIs will actually win over users. You know this because you know friends or family or colleagues who are aware of Debian and still don't choose it because they rely on some proprietary service or API that Debian's community developers have never given a rat's ass about.
In relative terms, Linux market share is increasing and Windows market share is declining.
> Good to know that Debian could have a fighting chance in a world where everyone had zero marketing budget and there weren't any rich corporate backers that used anti-competitive practices.
We could enforce the antitrust laws, yes.
> Anyway in the world we both live in, if Google abandoned Android then most people would instantly switch to a megacorp fork of Android with that megacorp's own proprietary APIs and services because people will follow the proprietary things they care about like for eg fast & battery-efficient centralized notifications, an out-of-the-box app store with popular apps like Instagram, and tap to pay.
None of that requires anything proprietary in the operating system.
Centralized notifications are implemented as a lock-in mechanism. Idle TCP connections don't consume battery unless they need keepalives, and in the latter case you provide applications with a non-proprietary API to have the OS handle keepalives by sending them together for any open connections that need them. Then the radio only has to wake up the same number of times it does with a single connection and there is no real advantage to centralization.
App stores are likewise only glued to operating systems for anti-competitive reasons. Spending 30 seconds once to install one that didn't come with the OS is such a low barrier that it can't be the thing preventing anyone from choosing an OS, and apps can be listed in more than one store, so there is no reason to expect any one store to dominate the market in the absence of anti-competitive practices.
The way tap to pay ought to work is you tap to get a payment request from the merchant which is then passed to your bank app using a standard protocol to make the payment, and then money is transferred from your bank to the merchant's bank with no intermediaries leeching a percentage. In the absence of sane regulations allowing this, you could also use any existing payment processors, but this is still something that an app does and not something that the OS does and the app doesn't have to be from the same entity as the OS.
> You know this because "millions of people" is derived from you knowing that the peak Linux desktop marketshare is like 4% out of billions of people.
Once again, Debian isn't what came with their computer. "Most people keep the defaults" works the other way when the default is Android.
> You know this because you said users are "worrying about losing access to those [proprietary, spying] APIs" which is why megacorps who provide these proprietary spying APIs will actually win over users.
The proprietary APIs don't provide anything good, they exist for the purpose of lock-in, because then third party developers use them without realizing or caring that it creates a dependency on proprietary code or services, since the existing installed base of phones that don't provide them is negligible.
Linux often does provide implementations of these things (e.g. wine), and certainly provides its own non-proprietary alternatives to them, but because the purpose of those things is lock-in the incumbent takes measures to prevent interoperability.
If there was no one providing proprietary APIs to begin with, or the antitrust laws were being enforced as they ought to be, that wouldn't be an issue. As it is, Linux market share keeps going up, but slowly, because the incumbents fight tooth and nail to keep the users in their cages.
The basic argument is we all either benefit or struggle more when the work of the people, for the people, is locked up in proprietary closed tools and data formats.
When open tools and data are employed, anyone can step up to improve those tools, and the State can fund the creation and maintenance of necessary tools and when that is done the savings over longer dpans of time.
A simple example:
PDX needed water billing. A 40 million bid was tendered and a private company created a system that they own and the State Basically pays them to use. And the State pays for fixes etc too.
What happens when a 40 million dollar investment is made in people using open code to do the same thing?
Well, the State owns the tool, and the data is open meaning anyone needing access can use open tools for that purpose.
When it matures, the org that got it done can fade away, leaving a small crew to maintain
, or
Maybe that org approaches other municipalities interested in similar savings. Over time, that problem is solved and most of the nation is enjoying a great savings and developers make a fine living, etc..
Wash rinse and repeat to reduce the cost of government and the work of the people is lean, mean, effective.
Everyone enjoys the benefit of a lower cost environment too.
This had broad bipartisan support and who pushed it away?
Big companies paid lobby shut the effort down hard.
They could very easily see the popular appeal and chose to spend huge now to shit it down, paying the house speaker to block it all from having a vote.
It was going to pass easily.
I think many governments can see how to think this way.
Big companies do not want it.