3 ms·
> This was clearly intended to eventually replace Android and ChromeOS I worked at Google (on the Chrome team) for years while Fuchsia was getting started. Re
by dmazzoni 3y ago
> This was clearly intended to eventually replace Android and ChromeOS
I worked at Google (on the Chrome team) for years while Fuchsia was getting started.
Replacing Android and Chrome OS would have made so much sense, but they were definitely NOT trying to do that. I never understood why.
They had a great plan for an OS that lived in a complete vacuum, with absolutely no plan to gain adoption or transition any existing platform to it.
It was literally tech for the sake of tech, and it made no sense.
- medstrom 3y agoCan't speak for management, but they could've seen it as funding open-ended research. Give a bunch of nerds freedom from shipping dates, deadlines, adoption plans, customer demands, and other such things that they always complain about, then see what they come up with. It's expected that this kind of strategy will yield nothing most of the time, but eventually you get a positive Black Swan.
- IshKebab 3y ago> Replacing Android and Chrome OS would have made so much sense, but they were definitely NOT trying to do that. I never understood why. Are you sure? In my experience people often say that project X isn't intended to replace project Y when it absolutely is, in order to avoid having to fight the people working on project Y. An open source example of this is WASM. When it first appeared there were countless "wasm isn't intended to replace JavaScript" claims. Of course it 100% was (for a number of use cases anyway), but people had to say that to placate the JS fanatics. It looks like Google potted ART to Fuchsia at one point.
- dmitrygr 3y agoART is a compiler. Its main OS interaction is file access. I can port it to MS-DOS for you in a week of free time. What will that prove?