←back to thread

521 points OlympicMarmoto | 1 comments | | HN request time: 0.232s | source
Show context
dmazzoni ◴[] No.45070781[source]
I was at Google when the Flutter team started building Fuchsia.

They had amazing talent. Seriously, some of the most brilliant engineers I've worked with.

They had a huge team. Hundreds of people.

It was so ambitious.

But it seemed like such a terrible idea from the start. Nobody was ever able to articulate who would ever use it.

Technically, it was brilliant. But there was no business plan.

If they wanted to build a new kernel that could replace Linux on Android and/or Chrome OS, that would have been worth exploring - it would have had at least a chance at success.

But no, they wanted to build a new OS from scratch, including not just the kernel but the UI libraries and window manager too, all from scratch.

That's why the only platform they were able to target was Google's Home Hub - one of the few Google products that had a UI but wasn't a complete platform (no third-party apps, for example). And even there, I don't think they had a compelling story for why their OS was worth the added complexity.

It boggles my mind that Fuchsia is still going on. They should have killed it years ago. It's so depressing that they did across-the-board layoffs, including taking away resources from critically underfunded teams, while leaving projects like Fuchsia around wasting time and effort on a worthless endeavor. Instead they just kept reducing Fuchsia while still keeping it going. For what?

replies(10): >>45070811 #>>45070831 #>>45070855 #>>45071001 #>>45071564 #>>45071591 #>>45071941 #>>45072113 #>>45072863 #>>45079620 #
surajrmal ◴[] No.45071591[source]
It's a lot of work and hard to justify if you're looking for short term improvements. But if you're really committed to long term improvements, it absolutely makes sense. Google is actually willing to make long term investments. Publicly justifying the investment has never been a goal of the project which is why most folks probably don't understand it. Honestly I'm not sure why folks care enough to even do commentary on it. If you find it useful, you can participate, if not just ignore it.

Fwiw inventing a new application ecosystem has never been a goal and is therefore not a limitation for its viability. The hard part is just catching up to all the various technologies everyone takes for granted on typical systems. But it's not insurmountable.

I'm also not sold on the idea that having more options is ever a bad thing. People always talk about web browser monoculture and cheer on new entrants, yet no one seems to mind the os monoculture. We will all come out ahead if there are more viable OS out there to use.

replies(1): >>45071918 #
1. touristtam ◴[] No.45071918[source]
> People always talk about web browser monoculture and cheer on new entrants, yet no one seems to mind the os monoculture. We will all come out ahead if there are more viable OS out there to use.

3 main OSes vs 2 main browser engine for consumer to choose from?

Anyway the main issue with the Browser engine consolidation is that whoever owns the Browser engine, can make or break what goes in there. Just think about VSCode's current status with all the AI companies wanting to use it and make it their own product, while MSFT attempting to curtail it. At some point either MSFT decide it commit to FOSS on this one, or the multiple forks will have to reimplement some functionalities.