OpenAI, Perplexity AI and Yahoo have expressed interest in buying Chrome, as Google's legal battle escalates. Here's what it could mean for the future of the web.
The primary ways in which the Mozilla Foundation earns money is through search partnerships, donations and grants.
Yes. It’s the same thing with the Linux kernel and other large FOSS projects. There isn’t a perfect fit for Android, but it would be better than the way ASOP is run now.
As for Red Hat, this comes down to subscriptions or enterprise offerings, neither which really apply to a consumer OS unless you’re willing to pay a subscription fee out of pocket.
Consumer devices ship with proprietary software which is licensed all the time. It could be a library or an entire OS. Consumers are not the target market, like consumers aren’t the target market for RHEL.
The prime example is Windows. It’s licensed to Dell or whomever and ships with the hardware. The license is baked in.
Some people might be willing to pay if the price is reasonable enough. Android has support for major vendors, so using it as a base would be a boon to people doing things like media boxes and signage.
I doubt there will be much to be earned from offering consulting or training, either, unless they make Android exceedingly confusing to use.
It’s the opposite. Make it easy to use. Companies pay for tools which reduces developer time.
The only companies that would pay for Android are OEMs who are already making thin margins, and effectively it’d drive the price of non-iPhones up.
The smaller OEMs would pay for licenses, PS hours, and backend services. They don’t have the expertise or budget.
Samsung? They’re going to keep doing what they’re doing because they have the expertise and budget to fork from upstream. It’s possible they would rally around Android, like companies have rallied around the Linux kernel.
OEMs do this with Linux already, so it would bring Android more inline with the norms.
It’s funny you should mention this, because Google has needed to adapt this for mobile and are already open source. If the opportunity existed for a “free” and open source version of Android to be embraced by consumers, there are many such options today, like GrapheneOS (or even forking AOSP, for that matter).
My concern is that if the major contributor to that steps out, the volunteer community will need to substantially step up.
Consumer devices ship with proprietary software which is licensed all the time
The reason I called out your example of Red Hat is to illustrate how enterprise is financing a free consumer experience.
With a very limited enterprise market, it’s not realistic to expect this to apply to an almost exclusively consumer product.
So there are two options. Either we don’t have an open source Android and in addition to the license cost of GMS, OEMs would have to license the OS itself. The alternative is that OEMs shoulder the development cost of their own fork of AOSP, which would simply be passed on to consumers. Either way, this would drive up the price of devices.
I’m not sure why you’re speaking in hypotheticals about what Android could be if it had license fees, as it’s readily available in open source under the Apache license today and, despite that, steadily losing market share.
Yes. It’s the same thing with the Linux kernel and other large FOSS projects. There isn’t a perfect fit for Android, but it would be better than the way ASOP is run now.
Consumer devices ship with proprietary software which is licensed all the time. It could be a library or an entire OS. Consumers are not the target market, like consumers aren’t the target market for RHEL.
The prime example is Windows. It’s licensed to Dell or whomever and ships with the hardware. The license is baked in.
Some people might be willing to pay if the price is reasonable enough. Android has support for major vendors, so using it as a base would be a boon to people doing things like media boxes and signage.
It’s the opposite. Make it easy to use. Companies pay for tools which reduces developer time.
The smaller OEMs would pay for licenses, PS hours, and backend services. They don’t have the expertise or budget.
Samsung? They’re going to keep doing what they’re doing because they have the expertise and budget to fork from upstream. It’s possible they would rally around Android, like companies have rallied around the Linux kernel.
OEMs do this with Linux already, so it would bring Android more inline with the norms.
It’s funny you should mention this, because Google has needed to adapt this for mobile and are already open source. If the opportunity existed for a “free” and open source version of Android to be embraced by consumers, there are many such options today, like GrapheneOS (or even forking AOSP, for that matter).
My concern is that if the major contributor to that steps out, the volunteer community will need to substantially step up.
The reason I called out your example of Red Hat is to illustrate how enterprise is financing a free consumer experience.
With a very limited enterprise market, it’s not realistic to expect this to apply to an almost exclusively consumer product.
So there are two options. Either we don’t have an open source Android and in addition to the license cost of GMS, OEMs would have to license the OS itself. The alternative is that OEMs shoulder the development cost of their own fork of AOSP, which would simply be passed on to consumers. Either way, this would drive up the price of devices.
I’m not sure why you’re speaking in hypotheticals about what Android could be if it had license fees, as it’s readily available in open source under the Apache license today and, despite that, steadily losing market share.