9 ms·
It was unfortunately obvious that the writer had insufficient tech chops when use the phrase "a post-API programming model" But pressing on how somehow manage
by michaelmrose 10y ago
It was unfortunately obvious that the writer had insufficient tech chops when use the phrase
"a post-API programming model"
But pressing on how somehow manages to blame the lack of updates to android phones on the modularity of the Linux kernel. The joke of course being that linux is monolithic and googles new OS is a microkernel ergo more modular.
The quote is "...however. I also have to imagine the Android update problem (a symptom of Linux’s modularity) will at last be solved by Andromeda"
Its hilarious that he can somehow defying all sanity ascribe androids update issue to an imagined defect in Linux. Android phones don't get updated because for the manufacturers ensuring their pile of hacks works with a newer version of android would represent a non trivial amount of work for the oem whom already has your money. The only way they can get more of your money is to sell you a new phone which they hope to do between 1-2 years from now.
In short offering an update for your current hardware would simultaneously annoy some users who fear change, add little to those who plan to upgrade to a new model anyway, decrease the chance that a minority would upgrade, and cost them money to implement.
Its not merely not a flaw in the underlying linux kernel its not a technical issue at all.
- bjarneh 10y ago> would represent a non trivial amount of work for the oem whom already has your money This is it; unless crucial apps (or some other necessity) only work with a newer Android version (which could push OEM's to update) they never will. Much better for OEM's to hope that you'll "update Android" through the purchase of a new phone.
- coredog64 10y agoThe carriers bear some blame as well. Apple negotiated for the right to upgrade the OS without carrier review, but most Android device OEMs don't. So the carriers drag their feet as well, hoping you'll buy that new device from them and be locked in for another 2 years.
- fauigerzigerk 10y ago>The only way they can get more of your money is to sell you a new phone which they hope to do between 1-2 years from now. Right, but they will never get my money if they don't deliver timely OS updates for the old model. You're right of course that this issue has absolutely zero to do with Linux.
- Merovius 10y ago> It was unfortunately obvious that the writer had insufficient tech chops when use the phrase That's a direct quote from the linked page. Unless you are suggesting that the authors of fuchsia have "insufficient tech chops".
- kpil 10y agoThey can be caught up in the same functional stupidity as everyone else at a large corporation. If someone important enough says "decouple" and "monolith are bad" often enough, those arguments will be used to support more or less all changes as they already got leverage in the organisation. The actual reasons could be something else, possibly as simple as they would like to control the OS, and possibly also that it's cool to write OSes.
- mtgx 10y agoBoth of you are half-right. It's not an underlying technical Linux issue, but it does come from Linux's "everyone can have one" ecosystem model. While on Windows and macOS there is only one master, so only one master can be responsible for the updates. So either Google fully controls Andromeda, as it does with Chrome OS, so it can update it (Google could probably still release an open source "Andromedium" version later on, like it does with Chromium OS), or it somehow forces all OEMs to update on time right from the beginning. But the later sounds like a real pain from Google's perspective, as it would probably have to one day completely retract Samsung's license for instance, or sue it, if Samsung doesn't comply, and this could create all sorts of PR problems for the Google. Or Google would have to compromise and allow the OEMs to delay updates from say 1 month to 3 months or more. And then we'd be right back to square one. I don't think there's a real practical solution to the update problem other than Google fully controlling the codebase. > The joke of course being that linux is monolithic and googles new OS is a microkernel ergo more modular. If you're suggesting that because the microkernel is modular that means "it should solve the update problem", I disagree. I don't think it would be much better than what we have now. Sure, it may be easier for Google, or say Samsung, to update their modules faster. But what about the other modules in the market? Will they be updated just as fast by noname OEMs? Probably not.
- pjmlp 10y ago> The only way they can get more of your money is to sell you a new phone which they hope to do between 1-2 years from now. The thing is, this only works on countries similar to US where most people are on contracts. In the rest of the world, where people are on pre-paid, we use our phones until they either die or get stolen, which is way more than just 1-2 years.
- Dylan16807 10y agoReplace 2 years with 7 years and the logic doesn't change.
- bhaavan 10y ago> until they either die or get stolen or screen cracked or phone soaked in water (but these problems will diminish when IP68 and Gorilla Glass 5 become more mainstream)
- dx034 10y agoThey say that for every new Gorilla glass. It'll always be super resistant against anything. Yet, the newest iPhones still scratch if you just have them in the same pocket as your keys for more than a day (personal experience). And it's still very easy to destroy the screen if the phone drops once (even though less of the screen will crack nowadays). We are very far away from phones that you could use without screen protection and not see damages after 1-2 years. For a device that is supposed to be carried around all the time, modern phones show little resistance against scratches. But maybe that's just not possible to archive.
- TeMPOraL 10y agoScratches are one thing; you can work around them with disposable screen protectors. But we're talking about a device that's constantly carried around and used (I probably have my phone on me more often than my wallet). Gorilla glass or not, it falls from a meter onto a hard surface, and you have a screen to replace. You accidentally sit on it, and you may have a screen to replace. And given the prices of replacement parts, it often makes sense to just live with the crack[0] until you get a new phone, which is probably why I see so many people with spiderwebs on their phones every day. -- [0] - Unless you want to take a risk and get someone to replace you just the broken glass, a process which involves some manual fumbling with heatguns and UV-hardened glues. Or, unless you live in Shenzhen, where they'll replace you the whole phone front (with electronics and all) for cheap, if you give them your phone front (which they presumably fix up later and resell to the next person).
- pjc50 10y agoThere's one design decision in Linux that makes this slightly harder than it needs to be in this situation: Linux's lack of a driver ABI. At the moment, phones include all sorts of custom drivers for very specific versions of the hardware. The OEMs ought to send these upstream, but don't want to. You can't build your own kernel and upgrade without breaking all the binary-only drivers. Android falls between two stools. Google own the userland but the OEMs are responsible for updates and the SOC manufacturers (mostly Qualcomm and Mediatek) are responsible for closed-source drivers. Arguably the cleanest and least achievable way out of this is trying to have an OS-only phone.
- dTal 10y ago>The OEMs ought to send these upstream, but don't want to. Isn't this a rampant GPL violation? Why do we put up with this? We are about to lose the war for general purpose computing due to insufficient GPL enforcement.
- JumpCrisscross 10y ago> Why do we put up with this? Who is "we"? As in, who will pay the lawyers?
- deleted 10y ago[deleted]
- syshum 10y agoSoftware Freedom Conservancy has been saying this for a long time, most the Kernel Devs, Linux Foundation, etc all seem to want to treat the Linux Kernel more like BSD than GPL. They do not want to piss of their corporate masters..
- kristoffer 10y agoNo it's not a "rampant" violation. Some people believe it is a violation and some not. Linus Torvalds being one who thinks its's fine. See e.g. https://lkml.org/lkml/2006/12/14/218 https://lkml.org/lkml/2006/12/14/218
- kodroid 10y agoNot only the OEM hacks but also supporting various hardware
- DCKing 10y ago> Android phones don't get updated because for the manufacturers ensuring their pile of hacks works with a newer version of android would represent a non trivial amount of work for the oem whom already has your money. The only way they can get more of your money is to sell you a new phone which they hope to do between 1-2 years from now. The fact you need Android device OEM's support is precisely the problem here, and that's mostly (mostly - admittedly not entirely) to blame on the way that manufacturers need to update their Linux kernels. Linux' monolithic nature makes this a major pain, especially since component manufacturers (for the SoC, touchscreen, fingerprint reader, camera sensor) implicitly require maintaining some non-mainline Linux. The manufacturer now serves as the central hub coordinating this 'mess' to update their devices. Mostly (again, not entirely) due to Linux, Android updates are dependant on manufacturers compiling update packages which are essentially full system upgrades. Each time they make an upgrade for a phone, they need to make an entire new device image. The manufacturers have clearly shown to be incapable of handling this responsibility, both in terms of their abilities as well as their motivations. A more modular OS would go a long way in taking away these responsibilities, since it will be technical means by which responsibilities can be given to a better motivated third party. Clearly we should be looking towards a model more akin to Microsoft Windows, where there's a more stable driver API/ABI for drivers, that allows the OS' original manufacturer to update critical components and introduce new features without depending on an incapable/unwilling manufacturer. Make system updates not full system upgrades, but make the system able to update some components with reasonable confidence that things will keep on working. With such a system Google or the "Open Handset Alliance" - or depending on the openness of this new Andromium, others like the LineageOS community - can take care of updating phones instead of the device OEM. In such a scenario you might still be stuck on graphics drivers from several years ago with serious rendering bugs, but at least security issues like Stagefright [1] and Dirty COW [2] can be effectively dealt with in a matter of days. That's a huge improvement over the current situation, where the majority of Android devices are still affected by both issues, years or months after their publication. Imagine how unlucky we should be to be fully dependant on Asus or LG for software support on our laptops. But that's exactly the situation on our phones. [1]: https://en.wikipedia.org/wiki/Stagefright_(bug) https://en.wikipedia.org/wiki/Stagefright_(bug) [2]: https://en.wikipedia.org/wiki/Dirty_COW https://en.wikipedia.org/wiki/Dirty_COW
- snvzz 10y ago> Its not merely not a flaw in the underlying linux kernel its not a technical issue at all. I believe he's talking about having a driver API. Fuchsia also runs its drivers in userspace, which is the proper design in a post-Liedtke world. (principle of minimality)
- pmilot 10y agoEven when talking about driver updates, the argument is nonsensical. Android updates already require a full reboot of the device at the end of the update process, so new drivers can (and are) already be loaded into the kernel. The update problem on Android is indeed a policy issue, not a technical one.
- syntheticnature 10y agoBased on what I've seen elsewhere in these threads, the idea is that a stable driver ABI means that manufacturers/chipmakers need not rewrite drivers just because there is a kernel update, removing that as a block to doing said kernel update. The willingness of Qualcomm to do the driver updates for a given chip to work with the latest kernel in Android was a big determiner of which phones have any chance of getting the latest Android, for example.
- usrusr 10y ago> The only way they can get more of your money is to sell you a new phone which they hope to do between 1-2 years from now. Which is why I would absolutely love to see a hardware vendor adopt paid updates, with a mission statement along these lines: "we cannot believably promise a reliable progression of software updates, because too many before is have tried and failed. What we can do, however, is rewrite the rules so that we will have a much stronger incentive to follow through than or predecessors".
- Lawtonfogle 10y agoCould that back fire? There are cases where humans judge taking no action because it avoids costs as inherently better than taking action to bring in profit even when others in general are better off. I could see a lot of people getting mad at being charged for updates which cost money who wouldn't get mad when there are no updates because the company doesn't want to lose money making free updates. It's almost like a section of society judges not helping as better than helping for some price, even though anyone who doesn't want to pay is no worse off than if they were never given an option. I see this trend outside of business as well.
- usrusr 10y agoIt would certainly not be good business for a consumerism-centered brand like Samsung and it would even be suicidal for Apple to suddenly start charging for updates. But for an Android brand built around sustainability, like e.g. Fairphone, it could be a considerable credibility gain if they replaced a promise of future gifts with a proposal for future business. No matter how updates happen, if they do the effort will be paid for with money coming from the customer, one way or the other. Any payment scheme other than pay on delivery requires trust and that specific form of trust has evaporated a long time ago.
- devenvdev 10y agoFunny, today we were talking with my co-workers about the new Samsung ads... "Samsung A5 - a new Samsung every year" Samsung A5 - more than you need" Rediculous...
- socmag 10y agoJust for correctness sake, the quote from the article: "a post-API programming model" looks like it came directly from the source repo. https://fuchsia.googlesource.com/modular/+/master https://fuchsia.googlesource.com/modular/+/master /----------------- Modular Modular is the application platform of Fuchsia. It provides a post-API programming model that allows applications to cooperate in a shared context without the need to call each other's APIs directly. /-----------------
- kyrra 10y agoAnd even if they upstream their changes, whatever versions of Android they are trying to get in at launch would still need the changes back ported to whatever kernels those run. Plus you're not guaranteed that android will move to whatever kenrel version the upstream changes landed in.