Google is officially releasing its Fuchsia OS, starting w/ first-gen Nest Hub
Google's long-in-development, from-scratch operating system, Fuchsia, is now running on real Made by Google devices, namely, the first-generation Nest Hub.
Google has told us that as of today, an update is beginning to roll out to owners of the first-generation Nest Hub, first released in 2018. For all intents and purposes, this update will not change any of the functionality of the Nest Hub, but under the hood, the smart display will be running Fuchsia OS instead of the Linux-based "Cast OS" it used before. In fact, your experience with the Nest Hub should be essentially identical. This is possible because Google's smart display experience is built with Flutter, which is designed to consistently bring apps to multiple platforms, Fuchsia included.
We've been tracking the development of Fuchsia since 2016, starting from an ambitious experimental UI, to running on Google's many internal testing devices for Fuchsia, ranging the full gamut of Google's smart home and Chromebook lineup. In the time since then, the OS has gradually progressed and recently even begun a steady release schedule.
Also at The Verge and Notebookcheck.
Previously:
Google's Not-So-Secret New OS
Google Fuchsia UI Previewed
Google to Add Swift Language Support to Fuchsia OS
Google's Fuchsia OS Adds Emulator for Debian Linux Applications
Google's Cross-Platform Flutter SDK Moves Out of Beta With Release Preview 1
Google Hopes to Replace Android with Fuschia in Five Years
Now Is the Time to Start Planning for the Post-Android World
Google Hires a 14-Year Apple Veteran to Bring Fuchsia to Market
Related Stories
Google is designing a new operating system (also at Github) based on its own new kernel (Magenta), which may be intended to unify/replace Android and ChromeOS. It is also expected to run on a wide range of ARM and x64 devices, such as Chromecast, Raspberry Pi 3, smartphones, laptops, and desktops.
TechSpecs Blog ponders:
I decided to dig through open source to examine the state of Google's upcoming Andromeda OS. For anyone unfamiliar, Andromeda seems to be the replacement for both Android and Chrome OS (cue endless debates over the semantics of that, and what it all entails). Fuchsia is the actual name of the operating system, while Magenta is the name of the kernel, or more correctly, the microkernel. Many of the architectural design decisions appear to have unsurprisingly been focused on creating a highly scalable platform.
It goes without saying that Google isn't trying to hide Fuchsia. People have clearly discovered that Google is replacing Android's Linux kernel. Still, I thought it would be interesting for people to get a better sense of what the OS actually is. This article is only intended to be an overview of the basics, as far as I can comment reasonably competently. (I certainly never took an operating systems class!)
To my naive eyes, rather than saying Chrome OS is being merged into Android, it looks more like Android and Chrome OS are both being merged into Fuchsia. It's worth noting that these operating systems had previously already begun to merge together to an extent, such as when the Android team worked with the Chrome OS team in order to bring Update Engine to Nougat, which introduced A/B updates to the platform.
Google is unsurprisingly bringing up Andromeda on a number of platforms, including the humble Intel NUC. ARM, x86, and MIPS bring-up is exactly what you would expect for an Android successor, and it also seems clear that this platform will run on Intel laptops.
Google's Fuchsia System UI can now be previewed. The operating system could potentially replace Android and even ChromeOS:
Google, never one to compete in a market with a single product, is apparently hard at work on a third operating system after Android and Chrome OS. This one is an open source, real-time OS called "Fuchsia." The OS first popped up in August last year, but back then it was just a command line. Now the mysterious project has a crazy new UI we can look at, so let's dive in.
Unlike Android and Chrome OS, Fuchsia is not based on Linux—it uses a new, Google-developed microkernel called "Magenta." With Fuchsia, Google would not only be dumping the Linux kernel, but also the GPL: the OS is licensed under a mix of BSD 3 clause, MIT, and Apache 2.0. Dumping Linux might come as a bit of a shock, but the Android ecosystem seems to have no desire to keep up with upstream Linux releases. Even the Google Pixel is still stuck on Linux Kernel 3.18, which was first released at the end of 2014.
[...] This all leads us to an interesting point right now: the Fuchsia interface is written with the Flutter SDK, which is cross-platform. This means that, right now, you can grab chunks of Fuchsia and run it on an Android device. Fuchsia first went public in August 2016, and but back then compiling it would get you nothing more than a command line. Thanks to Hotfixit.net for pointing out that the Fuchsia System UI, called "Armadillo" is actually pretty interesting now.
It's possible to download the source and compile Fuchsia's System UI into an Android APK and install it on an Android device. It consists of a wild reimagining of a home screen along with a keyboard, a home button, and (kind of) a window manager. Nothing really "works"—it's all a bunch of placeholder interfaces that don't do anything. There's also a great readme in the Fuchsia source that describes what the heck is going on.
It's about time for Linux Torvalds' domination of the smartphone industry to end.
Also at BGR, ZDNet, ComputerWorld, and The Register. Preview video.
Google will contribute changes to Apple's Swift programming language, and will support the language in the Fuchsia OS, a presumed replacement for Android, ChromeOS, etc. that is designed to work on all devices:
Fuchsia is Google's not-at-all-but-kind-of-secret operating system that's being developed in the open, but with almost zero official messaging about what it's for, or what it's built to replace. (Android? Chrome OS? Both? Neither?) The operating system's core is written in mostly C and C++, with Dart for the default "Flutter" UI, but other languages like Go, Rust, Python, and now Swift have also found a home in the project.
Of course, just because you'll be able to compile Swift to run on Fuchsia doesn't mean you'll be able to instantly port any iOS app to Google's new OS when or if it ships. While Apple has open sourced the Swift language itself, much of the iOS platform (like the UI stuff, for instance) is closed source, so code that relies on those closed Apple libraries won't be portable.
One possible future in a world where Fuchsia is an important and relevant platform for apps is that you write the "core logic" of your app in your language of choice — Swift, Go, Rust, JavaScript, etc. — and then you build a custom UI for each platform — Android, iOS, Fuchsia, Linux, Windows, the web — using the appropriate tools for each.
Also at Android Police.
Previously: Google's New Non-Linux OS: Fuchsia
Google's Not-So-Secret New OS
Google Fuchsia UI Previewed
Google's Fuchsia OS will support Linux apps
Google's non-Linux-based Fuchsia OS has added an emulator for running Debian Linux apps. Like its upcoming Linux emulator for Chrome OS, Fuchsia's "Guest" app will offer tighter integration than typical emulators.
Google has added a Guest app to its emergent and currently open source Fuchsia OS to enable Linux apps to run within Fuchsia as a virtual machine (VM). The Guest app makes use of a library called Machina that permits closer integration with the OS than is available with typical emulators, according to a recent 9to5Google story.
Last month, Google announced a Project Crostini technology that will soon let Chromebook users more easily run mainstream Linux applications within a Chrome OS VM. This week, Acer's Chromebook Flip C101 joined the short list of Chromebooks that will offer Linux support later this year.
Previously: Google's New Non-Linux OS: Fuchsia
Google's Not-So-Secret New OS
Google Fuchsia UI Previewed
Google to Add Swift Language Support to Fuchsia OS
ChromeOS Gains the Ability to Run Linux Applications
Google has updated a mobile framework that targets Android, iOS, and the in-development Google Fuchsia OS:
On Wednesday, Google's cross-platform mobile framework Flutter reached Preview Release 1, a designation that places the code somewhere between buggy beta and less buggy 1.0.
"The shift from beta to release preview signals our confidence in the stability and quality of what we have, and our focus on bug fixing and stabilization," said Google group product manager Tim Sneath in a blog post.
Introduced in May 2017, Flutter provides a way for Linux, macOS and Windows developers to create mobile apps in the Dart programming language that can run on Android, iOS or Google Fuchsia, an operating system that Google is working on.
Apps would be bundled with the Flutter engine:
Flutter is Google's second swing at a mobile SDK (the first being a little platform called "Android"). Flutter's claim to fame is that it's cross-platform—Flutter apps run on Android and iOS—and it's really fast. Flutter apps sidestep the app platforms of Android and iOS and instead run on the Flutter rendering engine (written in C++) and Flutter framework (written in Google's Dart language, just like Flutter apps). When it's time to ship a Flutter app off to Google's and Apple's respective app stores, the requisite Flutter engine code gets bundled up with the app code, and the Flutter SDK spits out Android and iOS versions of your single code base. Each version comes complete with built-in app themes for Android or iOS, so they still feel like native apps. Along with Android and iOS, Flutter is also the platform used for apps in Google's experimental Fuchsia OS.
Related: Google's New Non-Linux OS: Fuchsia
Google's Not-So-Secret New OS
Google Fuchsia UI Previewed
Google to Add Swift Language Support to Fuchsia OS
Bloomberg reports that Google's Project Fuchsia may eventually succeed Android.
Here's what's already known about Fuchsia: Alphabet Inc.'s Google started quietly posting code online in 2016, and the company has let outside app developers tinker with bits of the open-source code. Google has also begun to experiment with applications for the system, such as interactive screen displays and voice commands for YouTube.
But members of the Fuchsia team have discussed a grander plan that is being reported here for the first time: Creating a single operating system capable of running all the company's in-house gadgets, like Pixel phones and smart speakers, as well as third-party devices that now rely on Android and another system called Chrome OS, according to people familiar with the conversations.
According to one of the people, engineers have said they want to embed Fuchsia on connected home devices, such as voice-controlled speakers, within three years, then move on to larger machines such as laptops. Ultimately the team aspires to swap in their system for Android, the software that powers more than three quarters of the world's smartphones, said the people, who asked not to be identified discussing internal matters. The aim is for this to happen in the next half decade, one person said.
[...] The company must also settle some internal feuds. Some of the principles that Fuchsia creators are pursuing have already run up against Google's business model. Google's ads business relies on an ability to target users based on their location and activity, and Fuchsia's nascent privacy features would, if implemented, hamstring this important business. There's already been at least one clash between advertising and engineering over security and privacy features of the fledgling operating system, according to a person familiar with the matter. The ad team prevailed, this person said.
Glyn Moody over at the Linux Journal brings attention to the idea that Android's days are probably numbered and that it is time to consider viable exit strategies and file them for when they are needed later. Android is currently on over 2-billion devices around the world but the EU, goaded by Microsoft partners and proxies, has decided to fine Google 4.34 billion euros over Android for breaching EU antitrust rules weakening its usefulness. With an obvious replacement, Fuchsia, nearing completion at Google, and with the smartphone manufacturers also exploring alternative plans, such as Tizen and eelo, Android is starting to get alternatives. Just as the ages of CP/M, MS-DOS, and MS Windows have ended, so too will the current age of Android draw to a close. Eventually. Someday.
Previously on SN, Google Hopes to Replace Android with Fuschia[sic] in Five Years
Google has hired 14-year Apple engineer Bill Stevenson to help bring the Fuchsia OS to market.
We learned in 2016 that Google was working on an entirely new operating system called Fuchsia. Development continues with new features and testing on a variety of form factors spotted regularly. Google has since hired 14-year Apple engineer Bill Stevenson to work on its upcoming OS, and help bring it to market.
[...] Remaining in the OS X organization, he became a Senior Engineering Program Manager four years later. New responsibilities included serving as PM and Technical Lead for AirPlay, Find My Mac, iCloud for Mac, and AirDrop from 10.6 Snow Leopard to 10.9 Mavericks. Most of these features are notably backed by cloud services.
[...] It’s not surprising why Google would want someone with that background and experience to bring up Fuchsia. In a LinkedIn post shared yesterday, Stevenson specifically notes “joining Google to help bring a new operating system called Fuchsia to market.”
Google seems to be all aboard the Fuchsia train.
Previously: Google Hopes to Replace Android with Fuchsia in Five Years
Google's Fuchsia OS Adds Emulator for Debian Linux Applications
Google to Add Swift Language Support to Fuchsia OS
(Score: 5, Insightful) by fustakrakich on Wednesday May 26 2021, @03:14AM (1 child)
Followed quickly by the *end of life* schedule
La politica e i criminali sono la stessa cosa..
(Score: 1, Funny) by Anonymous Coward on Wednesday May 26 2021, @07:37AM
Let's not forget how it's meant to be pronounced in the first place - fucksya
(Score: 0, Funny) by Anonymous Coward on Wednesday May 26 2021, @03:55AM
townie: "I say, what are those Googles doing in the trees?"
farmer: "Nesting."
The OS wars, begun they have.
Huawei - launch their own OS. Unsurprising.
Google - finally replace Android, well a start has been made. Magenta was taken... T-Mobile, so "not-magenta" aka Fuschia.
MicroFart - all-new Windows Ten with brand new array of tentacles, coming soon(tm), etc..
(Score: 3, Interesting) by RamiK on Wednesday May 26 2021, @06:30AM (7 children)
Should have designed their own language instead of using C++. Now it's just another NT kernel with a different set of on-paper security features that refuse to work..
compiling...
(Score: 2) by looorg on Wednesday May 26 2021, @11:41AM (6 children)
I thought they were going to write it in Rust? Or did that change?
(Score: 2) by DannyB on Wednesday May 26 2021, @02:18PM
They were. But those plans were lost due to a memory leak bug.
The thing about landline phones is that they never get lost. No air tag necessary.
(Score: 3, Interesting) by RamiK on Wednesday May 26 2021, @03:17PM (4 children)
That was never on the table: https://fuchsia.dev/fuchsia-src/contribute/governance/policy/programming_languages [fuchsia.dev]
It's C++ for the kernel and Dart at the user facing user land. Everything else is just messing around where it doesn't really matter. But don't worry they're very open to other development models and 3rd party needs. Why, their 120 words introduction page [fuchsia.dev] even makes two separate mentions of "inclusiveness" in its 30 words "Principles" section.
compiling...
(Score: 2) by looorg on Wednesday May 26 2021, @08:30PM (3 children)
I found this kind of interesting, basically it's new and we don't know it so we won't support it.
They also dissed Go, their own language, and Python for being slow and horrid.
(Score: 3, Interesting) by RamiK on Wednesday May 26 2021, @11:29PM (2 children)
Survivor's bias: Anyone who chooses to develop something new in C++ is doing it since they're too cognitively invested in that skill-set to afford seriously learning anything else to a meaningful level of productivity.
compiling...
(Score: 2) by Socrastotle on Thursday May 27 2021, @03:36PM (1 child)
*Why* would you propose that a C++ programmer should move to a different language, to the point that you might believe the only reason he wouldn't would be inertia? Moving for the sake of moving is obviously absurd, so there must a reason to clearly demonstrate that not only is [hot new language] objectively superior to C++, but by an extremely substantial degree. The reason for this is that with C++ you have 40 years of development, enhancement, libraries, and other people using C++. Practically any issue you want to solve, any problem you run into, any library you might want, or basically anything is a quick search away. All of that's gone with [hot new language], and there's a very good chance that in 10 years [hot new language] will be sufficiently obscure to declare dead, even if it is still in use here and there.
And now you have a new little problem, whatever your answer might be. Let's imagine some language did offer something so compelling as to be able to meet this standard. Whatever amazing features this entailed would mean not only could C++ simply adopt them, but they likely would. See, for instance some of the changes [wikipedia.org] in C++ 11. It adopted a host of really great features that were offering some major productivity gains in other languages, and also added a mountain of handy exclusive tools as well. And that was in a single language update.
(Score: 2) by RamiK on Thursday May 27 2021, @07:44PM
I completely agree. The thing is, using existing 40 years old solutions suggests you have nothing "objectively superior" to existing ones. So, any general argument you're making for C++ is an argument you're making against Fuchsia.
That is, if Fuchsia is made from 40 years old tech, why not just use 40 years old tech?
compiling...