I think a large part of it is that they have little control over Android. Manufacturers put all their stuff and overlay on it. Imo it doesn’t work well and would be even worse with dual use and laptops. They have control of ChromeOS and make demands of anyone that wants to use it. I think they made a big mistake getting rid of Moto. They could have at least made their own devices free of other stuff.
ChromeOS is as open source as Android in the form of ChromiumOS. It just seems like there’s less desire to fork ChromiumOS and skin it since Linux already exists, and I assume most people would prefer to go to the source.
I agree that they should’ve kept Moto, but they do make (well, design, which is probably all Motorola did) their own handsets in the Pixel line. Pretty much everyone who puts their own badge on a phone these days designs it but has Foxconn assemble it using components sourced from other companies. The only company I’m aware of making their own silicon is Samsung.
I think a large part of it is that they have little control over Android. Manufacturers put all their stuff and overlay on it. Imo it doesn’t work well and would be even worse with dual use and laptops. They have control of ChromeOS and make demands of anyone that wants to use it. I think they made a big mistake getting rid of Moto. They could have at least made their own devices free of other stuff.
ChromeOS is as open source as Android in the form of ChromiumOS. It just seems like there’s less desire to fork ChromiumOS and skin it since Linux already exists, and I assume most people would prefer to go to the source.
I agree that they should’ve kept Moto, but they do make (well, design, which is probably all Motorola did) their own handsets in the Pixel line. Pretty much everyone who puts their own badge on a phone these days designs it but has Foxconn assemble it using components sourced from other companies. The only company I’m aware of making their own silicon is Samsung.