3 ms·
Your points don't jive with the success of ChromeOS. It doesn't have "native" apps, and runs Android and Linux applications via VMs. No one writing applications
by surajrmal 4y ago
Your points don't jive with the success of ChromeOS. It doesn't have "native" apps, and runs Android and Linux applications via VMs. No one writing applications targets ChromeOS as far as I know. They target chrome, steam, or Android. People don't write applications for OS anymore, they write applications for platforms which can be abstracted and ported to different OS.
- spencerchubb 4y agoThe unique UX ChromeOS provides is that chromebooks are only $200. The comment above is just asking how Fuchsia will provide a differentiated UX
- surajrmal 4y agoFuchsia isn't necessarily targeting end users or application developers. Fuchsia exists to make products easier to build and maintain. Products are responsible for the app developer and end user experience.
- pantalaimon 4y agoChromeOS is still Linux, it’s not a whole OS from scratch
- mike_hearn 4y agoGood point, but, you can argue that ChromeOS isn't actually the OS in that case. Linux and HTML5 are. ChromeOS is more or less a detail of the hardware that matters to admins who want/need total control and entirely cattle-like devices (the unique value prop). I agree with you though that people are mostly writing to abstraction layers. That's where the action is, which is why it's curious that Fuschia's approach isn't clearly a ChromeOS style "portable abstraction layer + shell to invoke abstracted apps". They use Dart and Flutter for the UI so in some ways it is, but then they have the whole component model and Fuschia specific APIs.