4 ms·
When I was there I was baffled by its sudden rise and the support it seemed to have from senior mgmt. My impression when it was announced was it started as a r
by cmrdporcupine 5y ago
When I was there I was baffled by its sudden rise and the support it seemed to have from senior mgmt.
My impression when it was announced was it started as a really neat personal project by some long-time OS development nerds (I mean that in a good way) that then escaped the gates and then it became a hammer in search of nails.
It ended up eating the project I was on, and was many many years late in the process of doing so, breaking schedule promise after schedule promise. I kept waiting for management to put a lid on it, but they seemed to have infinite headcount and budget, and patience from mgmt to support their mission to rewrite the world while we struggled to get time and resources to maintain the codebase we already had which was shipped as a profitable product and sitting in millions of people's homes with good reviews.
Google has OS politics dysfunction... especially in hardware devices where there are almost a half dozen Linux distributions fighting it out for marketshare. Fuchsia just added to that craziness.
- jstummbillig 5y agoCan you steel man the case for Fuchsia? What's the optimistic result that justifies this (apparently rather expensive) bet?
- cmrdporcupine 5y agoThe drivers situation for embedded Linux SoCs is awful. Fuchsia aims to fix that. Security model is better. Licensing I guess is easier to deal with. The OS structure is explicitly modeled for the kind of consumer hardware projects in question instead of, y'know, a PDP-11. None of this changes that the rollout for these things could be done incrementally in parallel with the existing Linux based platforms, with an eye to produce shared components whenever possible instead of rewriting the world. The Fuchsia folks were notorious for their obsession with purity of essence, and because they had the headcount and $$, they just did what they wanted.
- cogman10 5y agoFuchsia's driver handling is superior to what you get with linux. Because pretty much everything is pushed into userspace it makes it dead simple to keep a driver going forever. Were I to guess, the prime motivation for Fuchsia would be to have a phone or IoT device which could regularly receive kernel updates without needing hardware vendor interaction. That's the biggest sore spot for linux. (not that I think Fuchsia's kernel would require a bunch of updates due to how simple it is). This is an outsider's perspective. Definitely a big expensive project that reminds me of other big expensive google projects which seem DoA.
- cmrdporcupine 5y agoI don't think it will DoA. They shipped it on Nest Hub, and I'm sure they'll find other places to put it now. And yeah I think you're pretty on about the driver/vendor comment.
- oblio 5y ago> Fuchsia's driver handling is superior to what you get with linux. Because pretty much everything is pushed into userspace it makes it dead simple to keep a driver going forever. How does the lack of hardware vendor cooperation get improved by moving the problem into userspace? You still need/want the hardware vendors to create drivers and update them, which they frequently don't. I guess it's better because you're just going to be content with binary blobs?
- surajrmal 5y agoIt's common to conflate the idea of source availability with problems encountered by lack of binary stable interfaces. One of the problems with the status quo on Linux isn't that drivers aren't released as source, but that they aren't upstreamed. This causes the drivers to no longer be valid very quickly. If you solve the validity problem, folks can continue to release drivers, alongside their source and they will continue to be valid even as the rest of the operating system evolves. Just because Windows drivers tend to not have source available doesn't mean that it's a given the same will be true for fuchsia drivers. It is ultimately product makers who use fuchsia as a platform who drive the incentives for what driver authors do with their drivers.
- technofiend 5y ago>Security model is better. From the outside looking in I thought the security model could really help Google lower splash radius from zero days? The feature-set certainly sounds appealing just reading the marketing blurb. [1] With any luck in the next iteration Google will create a Fuschia ISO or VMDK so people who want to give it a spin without building it can quickly get a taste of the environment. The fact you can at least run it in an emulator is definitely a step up from requiring dedicated hardware, which was the previous process. [2] [1] https://fuchsia.dev/fuchsia-src/concepts/principles/secure https://fuchsia.dev/fuchsia-src/concepts/principles/secure [2] https://fuchsia.dev/fuchsia-src/development/hardware/paving https://fuchsia.dev/fuchsia-src/development/hardware/paving
- criddell 5y agoI believe Google can make a system that is secure from outside adversaries, but I'm less trusting that they would make an OS that isn't riddled with hooks for Google surveillance.
- getcrunk 5y agoCertainly. Sad thing is how many won't make the switch. I'm not judging, I'd do the same prolly due to pressures(ease of use, bandwagon, specific pain point fixes vs Linux)
- oblio 5y ago> The drivers situation for embedded Linux SoCs is awful. Fuchsia aims to fix that. How can they solve that with software? It's an incentive/economic problem. Hardware vendors don't want to play nice, there's no incentive for them. It's better if they're jerks and never release their stuff or do it years after their hardware stops being relevant.
- getcrunk 5y agoReplace and unify android, chromeos, their various iot devices. Eventually it becomes the base image for faas, app engine. Complete domination. Now if they have Microsoft/apple level os penetration you can be damn sure it's gonna be only serving google search. Just to ensure/build more moat aroing Google search can justify infinite cost
- PoignardAzur 5y ago>Now if they have Microsoft/apple level os penetration you can be damn sure it's gonna be only serving google search. Unless they want to do crazy things like sell to the EU market, in which case they're back to having to offer multiple search engines.
- sorry_outta_gas 5y agowell I mean, userspace would still be up in the air and there's no reason to have google search in a kernel right?
- getcrunk 5y agoYea, but I'm excited to see what a modern kernel can do that's master planned with our current knowledge. I don't know too much about the Linux kernel. But I imagine there's alot of cruft and inefficiencies because it grew over a long period of time in an ad hoc manner
- anon23anon 5y agoI'm on a project where money doesn't seem to matter and it's obnoxious.
- cmrdporcupine 5y agoIt produces toxic effects. Like an algae bloom.
- norswap 5y agoTbh, I would expect Google to have enough money to do both [develop new OS] and [maintain/improve existing products].
- cmrdporcupine 5y agoPlenty of money, but not enough discipline and focus to make that happen. After years in this industry and seeing so many things like this just fail, my perspective is that the "right" way to do it (rewrites/replatforms) is build shared components and have teams that deploy to both and so live in both worlds. This way the old gets the new, and the new has to live and breathe the reasons for the compromises that the old lived through the first time. And you don't end up with a "legacy" team and a "future" team. Example: I tried (a bit half-heartedly and I was low-status so nobody cared) to pitch that we write a new screenreader for Home Hub rather than brutally kludging in the one from ChromeOS. A new screenreader that could be shared with Fuchsia, as they were writing one from scratch. If building from scratch why not build one as a component that can be shared? That approach was seen as a total non-starter by the people I talked to. Fuchsia got to write their shiny new thing basically in isolation and barely interacted with us poor folk who had to keep maintaining the actual-existing screenreader deployed on several million devices in people's homes. Mainly fell to my friend/coworker who was a hero. BTW we both quit the same day.
- codeofdusk 5y agoAs a totally blind Home Hub user who finds Chrome Vox completely unsuitable for the platform, I'm saddened (though not surprised) that a Fuchsia screen reader never could see the light of day.
- surajrmal 5y agoI believe Fuchsia does have its own native screen reader. I have no idea if it's used on the home hub, but I would hazard a guess that it is. https://cs.opensource.google/fuchsia/fuchsia/+/main:src/ui/a11y/lib/screen_reader/screen_reader.h https://cs.opensource.google/fuchsia/fuchsia/+/main:src/ui/a...
- ihattendorf 5y agoNest Hub?
- AtlasBarfed 5y agoYou aren't a TRUE computing technology company without your OWN OS, bonus points for a boondoggle one. That's like a hypercar, not just a supercar. IBM has, what a half dozen between mainframes and AIX and older ones? Apple has their own OS of course. Microsoft of course. Facebook? Netflix? Amazon? Such second-rate "tech" companies, tsk tsk.