6 ms·
I think it's telling that they are 'launching' this with a product that barely matters in their product portfolio. That indicates to me that they don't see this
by jillesvangurp 5y ago
I think it's telling that they are 'launching' this with a product that barely matters in their product portfolio. That indicates to me that they don't see this as an Android killer just yet. A bold move would have been to put this on the next Pixel. Clearly, that's not happening. If that was at all feasible, they would have waited for that and that would have been the grand launch. So, clearly it's nowhere near ready for such a launch.
Their main issue with this is that OEMs like Samsung probably are not in any hurry whatsoever to jump on board and be even more dependent on Google. Without OEMs, app developers will drag their heels as well and Google is forced to maintain Android and not do a half-assed job of it. At this point Google has Android in cars, tvs, on phones, etc. Killing that would be suicidal; Google needs users interacting with their ads.
If they botch the Fuchsia launch somehow, they'd have more OEMs taking things in their own hands and cutting loose from Google and forking Android (like Amazon and Huawei already did). They clearly are not ready to pull the plug on Fuchsia just yet but at this point it's a more than likely outcome. IMHO, they should just rip off the band-aid and move on. Most of what is wrong with Android is fixable.
- dragonwriter 5y ago> I think it's telling that they are 'launching' this with a product that barely matters in their product portfolio. It’s certainly the best way to immediately get it a whole lot of real world use and feedback with basically zero sales effort, and its economical since it lets them transfer resources allocation from supporting a dead-end effort to a live one. > A bold move would have been to put this on the next Pixel. “Bold” is sexy, but not the same as smart long-term strategy in many cases.
- Daishiman 5y agoThere's a gigantic difference in developer effort to make an appliance OS versus a full-featured mobile OS.
- jillesvangurp 5y agoThey are clearly having commitment issues for that.
- Daishiman 5y agoI don't see it that way. Reinventing a mobile OS is a huge undertaking and it makes little sense to do it just as an experiment.
- remus 5y ago> I think it's telling that they are 'launching' this with a product that barely matters in their product portfolio. That indicates to me that they don't see this as an Android killer just yet. A bold move would have been to put this on the next Pixel. Clearly, that's not happening. If that was at all feasible, they would have waited for that and that would have been the grand launch. So, clearly it's nowhere near ready for such a launch. That seems like a good thing to me. Personally I'm not very interested in an OS that's 'bold', I want an OS that's stable and well tested and releasing slowly on a limited set of devices seems a good way of doing that.
- mamcx 5y agoContrast with Apple: M1 and pump! launched it the major selling laptop. That is how you know Apple mean business. And this is how you know fucsia/google will not.
- justapassenger 5y agoWhere else could've they launched it? It's not like Apple has tons of HW products that require M1. If Google would chose to launch Fuchsia as a base of next Android and force all OEMs on it, that would mean people managing release should be fired, as that's not how you stage major changes.
- mamcx 5y ago> and force all OEMs ???? This not make much sense, but if Google launched it in his own, then at least some OEMs could go along (supposing Fucsia is good, I don't know which could their selling point)
- izacus 5y agoApple has been launching the "M1" piece by piece for years now. They started with Qualcomm/PowerVR cores and ended up with custom designs over years of iterative product launches. I have no idea why do you think M1 is such a green field effort when it obviously shares so much of it's design with A series SoCs you've been seeing in your favorite iDevice.
- rvz 5y agoYou do realise that Apple's M1 processor + OS porting was a 10 year goal to produce the results that you see before you? Several years ago [0], the same ones here were calling Fuchsia dead since 2016 - 2018 and theoretically today it should already have died. Today Google has surprised the skeptics here and just released Fuchsia 1.0 on a real device (earlier than expected) and now you're already calling it dead again? This whole thread sounds like a Linux meltdown club to me. In fact, Google is taking / controlling Fuchsia in the same direction as to what Apple has always done with iOS / macOS and its own silicon. Perhaps when this decade ends, you will be looking at this comment (and this one [1]) via a phone running Fuchsia. [0] https://news.ycombinator.com/item?id=17568335 https://news.ycombinator.com/item?id=17568335 [1] https://news.ycombinator.com/item?id=22005286 https://news.ycombinator.com/item?id=22005286
- adrianmonk 5y agoAnother way of looking at it is that it probably takes a really long time to bring up an operating system to the point where it is production-ready. It would be easier to do if you can target one hardware platform that does not change so that you don't have to also shift gears. If you're building the Great Pyramid, you don't want to also move it to a new construction site when it's half-completed. Launching on hardware that was already released could mean they gave themselves that time. By the time they're finished (now), the hardware is old.
- summerlight 5y ago> A bold move would have been to put this on the next Pixel. Which will delay the next Pixel at least several years while causing a unprecedented level of fragmentation in the Android ecosystem? BTW, I don't expect this kind of experimental projects can live without reaching any milestones. Replacing Android with Fuchsia is just not a feasible option at this moment.