Google’s Fuchsia OS on the Pixelbook
arstechnica.com
Google’s Fuchsia OS on the Pixelbook
1–10 of 126 posts
Re: Google’s Fuchsia OS on the Pixelbook
#2There's no point to these early Fuschia review attempts. I don't see how it demonstrates anything. It's like looking at the famous first email from Linus Torvald and figuring out what the os would be in the end. So it boots, it has windows, but not apps, and prints some things to the screen. It tells us nothing about real intentions, future capabilities, etc.
Re: Google’s Fuchsia OS on the Pixelbook
#3There's no point to these early Fuschia review attempts. I don't see how it demonstrates anything. It's like looking at the famous first email from Linus Torvald and figuring out what the os would be in the end. So it boots, it has windows, but not apps, and prints some things to the screen. It tells us nothing about real intentions, future capabilities, etc.
Yeah, you can't "review" something that isn't even close to finished.
Windows Phone was originally supposed to eschew apps for some sort of focus on views, I forget what they called it. Now Windows 10 Mobile is more or less just Windows 10, with apps. I won't mind if someone finally finds a new model and makes it not suck, but when you're early in the product design phase is when you try crazy ideas to see if they pan out, the final product ends up looking more normal.
Re: Google’s Fuchsia OS on the Pixelbook
#4There's no point to these early Fuschia review attempts. I don't see how it demonstrates anything. It's like looking at the famous first email from Linus Torvald and figuring out what the os would be in the end. So it boots, it has windows, but not apps, and prints some things to the screen. It tells us nothing about real intentions, future capabilities, etc.
It's neat to see the progress even if you don't know where it's going. I wouldn't call it a 'review', though.
Re: Google’s Fuchsia OS on the Pixelbook
#5The code is available here:
https://fuchsia.googlesource.com/
Key components:
## Zircon
Zircon is the operating system's foundation: it mediates hardware access, implements essential software abstractions over shared resources, and provides a platform for low-level software development.
For example, Zircon contains the kernel, device manager, most core and first-party device drivers, and low-level system libraries, such as libc and launchpad. Zircon also defines the Fuchsia IDL (FIDL), which is the protocol spoken between processes in the system, as well as backends for C and C++. The backends for other languages will be added by other layers.
## Garnet
Garnet provides device-level system services for software installation, administration, communication with remote systems, and product deployment.
For example, Garnet contains the network, media, and graphics services. Garnet also contains the package management and update system.
## Peridot
Peridot presents a cohesive, customizable, multi-device user experience assembled from modules, stories, agents, entities, and other components.
For example, Peridot contains the device, user, and story runners. Peridot also contains the ledger and resolver, as well as the context and suggestion engines.
## Topaz
Topaz augments system functionality by implementing interfaces defined by underlying layers. Topaz contains four major categories of software: modules, agents, shells, and runtimes.
For example, modules include the calendar, email, and terminal modules, shells include the base shell and the user shell, agents include the email and chat content providers, and runtimes include the Dart andFlutter runtimes.
Re: Google’s Fuchsia OS on the Pixelbook
#6The code is available here: https://fuchsia.googlesource.com/ Key components: ## Zircon Zircon is the operating system's foundation: it mediates hardware access, implements essential software abstractions over shared resources, and provides a platform for low-level software development. For example, Zircon contains the kernel, device manager, most core and first-party device drivers, and low-level system libraries, s…
I like the naming even more than the architecture! :-)
Re: Google’s Fuchsia OS on the Pixelbook
#7I find it fascinating how polished the UI is even as it's missing core features.
Re: Google’s Fuchsia OS on the Pixelbook
#8This "review" is the video portion of this Ars Technica article: https://arstechnica.com/gadgets/2018/01/googles-fuchsia-os-o... which of course does not purport to be a review of Fuchsia.
Re: Google’s Fuchsia OS on the Pixelbook
#9The code is available here: https://fuchsia.googlesource.com/ Key components: ## Zircon Zircon is the operating system's foundation: it mediates hardware access, implements essential software abstractions over shared resources, and provides a platform for low-level software development. For example, Zircon contains the kernel, device manager, most core and first-party device drivers, and low-level system libraries, s…
I like the naming even more than the architecture! :-)
Which component are they going to name Steven?
Re: Google’s Fuchsia OS on the Pixelbook
#10There's no point to these early Fuschia review attempts. I don't see how it demonstrates anything. It's like looking at the famous first email from Linus Torvald and figuring out what the os would be in the end. So it boots, it has windows, but not apps, and prints some things to the screen. It tells us nothing about real intentions, future capabilities, etc.
Its sort of a "review" of an early preview. I think it demonstrates a lot especially what Fuchsia is and what it is capable of. The other point would be that Google gets free advertisements of their new OS.