3 ms·
No reason it can't be. Android has several big issues: 1. Lots of it is ugly. I don't mean the core OS, but lots of the apps don't fit the main theme. 2. It r
by IgorPartola 13y ago
No reason it can't be. Android has several big issues:
1. Lots of it is ugly. I don't mean the core OS, but lots of the apps don't fit the main theme.
2. It runs on diverse hardware so performance varies.
3. OS version segmentation. This is made worse by manufactures putting their own lipstick on the vanilla OS.
4. It's not proper FOSS. Yes, you can read the source at some point later, but chances of someone that's not Google, Motorola, Samsung, or HTC having their commit actually show up in the upstream are slim to none.
5. Phones and tablets are of varying quality and come with various levels of support. The manufacturer may back it, or they may drop support as soon as they can. Flagship phones become crap phones all the time.
Ubuntu may play their cards right and provide an integrated platform a la Apple's iOS devices, where software and hardware play nicely together. If they then insist on high quality apps, they may be able to get a foothold in the market. The question is, how long can the "crowd" support the right way of doing things before some exec somewhere says "We need it to have our own distinct UI"?
- mseebach 13y agoPoint 4 is orthogonal to the others. Points 1-3: If you have an proper, FOSS system, you can't keep people from doing all those things, which they will do if it gets get any kind of meaningful traction. Point 5: You can't force manufacturers to provide support at a certain level. You can probably avoid "TIVO-ization" with licensing, but as soon as you're venturing out of "supported" territory, there's only so much you can do for regular users.
- tjdetwiler 13y agoPoint 4 will apply to Ubuntu as well... they're using the Google/Android style FOSS where they work on major releases mostly in secret and then do a large code dump.
- polshaw 13y ago6. Java! Allowing core application code to be written in the languages we would chose to use for desktop applications (rarely java) would be a major advantage itself.
- dragonwriter 13y ago> It's not proper FOSS. Yes, you can read the source at some point later, but chances of someone that's not Google, Motorola, Samsung, or HTC having their commit actually show up in the upstream are slim to none. The second sentence doesn't support the first. FOSS isn't about whether you can get your commit accepted, its about your freedom to modify the source and use and share your modifications. FOSS and cathedral/bazaar development models are nearly orthogonal (they are logically orthogonal, though non-OSS bazaar is pretty rare and has some pragmatic difficulties.) Cathedral-style development model isn't "improper" FOSS.