Slashdot Mirror


Google's Mysterious Fuchsia OS Can Now Run On the Pixelbook (theverge.com)

Google's mysterious operating system, dubbed Fuchsia, has been in the works for more than a year now with very few details about the OS made public. According to a new report from Chrome Unboxed, we have learned that Google has released documentation to allow developers to load Fuchsia onto the company's Pixelbook. The Verge reports: This isn't your typical developer operating system, and you'll need two machines to host and target a Pixelbook to load the OS. It's very much a work in progress, with early hints at a user interface and functions. It's still interesting that Google has chosen its own Pixelbook to experiment with, though. Fuchsia has mostly been linked to embedded systems like wearables and Internet of Things devices in the past, but testing was expanded to Intel's NUC and Acer's Switch Alpha 12 Chromebooks. Fuchsia has been created from the Google-built Zircon microkernel, and not the typical Linux kernels that hold Android and Chrome OS together. It's not immediately clear exactly why Google is building a new operating system, nor what devices it will run on. As testing spreads to more Chromebooks, some are now speculating this could be a successor to the "Andromeda" project that never materialized.

60 comments

  1. This will likely be disastrous for Linux. by Anonymous Coward · · Score: 0, Interesting

    Fuchsia has been created from the Google-built Zircon microkernel, and not the typical Linux kernels that hold Android and Chrome OS together.

    I think that this will be disastrous for Linux.

    Linux has been floundering on the desktop for ages now, only ever getting perhaps 3% of the market.

    Linux has done slightly better in server and VM environments, but even then it faces some serious competition from the BSDs, Windows Server, Solaris, and other OSes. Many Linux users have reported problems involving systemd, which has already driven some server users away to other OSes, like FreeBSD.

    Linux has also seen some embedded usage, but these days it's mostly contained to Android on mobile devices. More serious users of embedded Linux have been moving to QNX and other realtime OSes for a while now.

    If we see future versions of Android, or perhaps an OS that replaces Android, become popular, it would effectively be removing most of Linux's market share. Linux would go back to being the kernel used on some servers, and a very small percentage of desktop systems.

    What's worse, I think that there's the real possibility that this new OS from Google could very well start eating into Linux's desktop and server market share, too, if this new OS ends up being usable in such environments.

    It sounds to me like Fuchsia OS could very well become the universal OS that we've all been waiting for: the OS that runs on embedded systems, through to mobile devices, through to servers, through to workstations, and perhaps even through to supercomputers and clusters.

    Linux could have been this universal OS, had the Linux community not bungled stuff up so badly with systemd, GNOME 3, Wayland, PulseAudio, and so on. But like so many times before, Linux has missed out on its true potential.

    It's looking more and more like Fuchsia OS will be the operating system of the future, with it competing against Windows and macOS, and with Linux becoming less and less relevant.

    1. Re: This will likely be disastrous for Linux. by zaivala · · Score: 1, Flamebait

      Solaris is dead, Windows Server almost dead. Systemd issues are mostly between old users' ears, people who like using hundreds of no-longer-supported programs to run their OS instead of a unified system which does it better.

    2. Re: This will likely be disastrous for Linux. by Anonymous Coward · · Score: 0

      Systemd issues are mostly between old users' ears, people who like using hundreds of no-longer-supported programs to run their OS instead of a unified system which does it better.

      s/no-longer-supported programs/programs that have been proven to work/

      s/does it better/can't be customized without a ridiculous amount of cost and effort/

  2. Quidquid id est... by demon+driver · · Score: 4, Interesting

    ..., timeo Danaos et dona ferentes. And no, I don't mean the Greek, and in case of Google or any such entity, it actually shouldn't be "even when they bear gifts", but "especially when they bear gifts".

    1. Re: Quidquid id est... by mapkinase · · Score: 0

      Is it really ferentes?

      --
      I do not believe in karma. "Funny"=-6. Do good and forbid evil. Yours, Oft-Offtopic Flamebaiting Troll.
    2. Re: Quidquid id est... by cervesaebraciator · · Score: 1

      It's "ferentis" in the Greenough edition. I could see "ferentes" being a variant reading though (much like "quidquid" in place of "quicquid"). Both -es and -is occur as accusative plurals for participles and adjectives of one ending.

    3. Re: Quidquid id est... by Anonymous Coward · · Score: 0

      Maybe "Timeo Danaos et dona Ferengis."

  3. Will it run on servers? by Anonymous Coward · · Score: 0

    I used to use GNU/Linux on my servers but I had to move to OpenBSD when systemd broke too often. Will Fuchsia eventually run on servers? I like OpenBSD on my servers but it's not a good OS on my laptop. I want to use the same OS on my dev laptop and my servers to make my life as a dev easier. If Fuchsia worked well on both my laptop and my servers then I would consider switching to it.

    1. Re:Will it run on servers? by TheFakeTimCook · · Score: 0

      I used to use GNU/Linux on my servers but I had to move to OpenBSD when systemd broke too often. Will Fuchsia eventually run on servers? I like OpenBSD on my servers but it's not a good OS on my laptop. I want to use the same OS on my dev laptop and my servers to make my life as a dev easier. If Fuchsia worked well on both my laptop and my servers then I would consider switching to it.

      Try this instead:

      https://stackoverflow.com/ques...

  4. Re:An opening for the competition by DarkRookie · · Score: 1

    Google is an $101.8 Billion company. I doubt they will lose any of that if this goes to the phones. Most people do not care.

    --
    The millennial that doesn't like most of the stuff designed for millennials.
  5. Anybody who doesn't understand what google is.... by Anonymous Coward · · Score: 0

    Doing, needs to go look at the history of microsoft, and the reason for Stallman pushing for the GPL at all levels of the stack.

    Google is creating a permissive/proprietary kernel that they will leverage for additional licensing leeway with their downstream manufacturers, as well as having the capability to close it at any time in order to leverage the extinguish phase of microsoft's three Es.

  6. Re:Anybody who doesn't understand what google is.. by Anonymous Coward · · Score: 0

    Doing, needs to go look at the history of microsoft, and the reason for Stallman pushing for the GPL at all levels of the stack.

    Google is creating a permissive/proprietary kernel that they will leverage for additional licensing leeway with their downstream manufacturers, as well as having the capability to close it at any time in order to leverage the extinguish phase of microsoft's three Es.

    License doesn't matter if the software is shit.

  7. NIH Syndrome by rahvin112 · · Score: 2, Interesting

    Google has always suffered from NIH syndrome. They will develop and abandon their own kernel rather than use the Linux kernel with billions of development hours because Google engineers didn't write linux.

    It really is that simple.

    1. Re:NIH Syndrome by jareth-0205 · · Score: 3, Insightful

      Google has always suffered from NIH syndrome. They will develop and abandon their own kernel rather than use the Linux kernel with billions of development hours because Google engineers didn't write linux.

      It really is that simple.

      What? They have been using a modified Linux kernel in Android and ChromeOS for nearly a decade now. They use a modified version of the kernel in their server farms. Clearly they are using Linux. Or is that not enough? They have to use it forevermore - Linux is the be-all-and-end-all of kernels, and can never be improved upon.

      I thought this was a tech site?

    2. Re: NIH Syndrome by omnichad · · Score: 1

      They are probably hitting a wall with low-power performance that can really only be solved by such extensive modification that a new kernel is easier at this point.

    3. Re:NIH Syndrome by Anonymous Coward · · Score: 1

      Google don't reinvent the wheel for its own sake, they used the Linux kernel for both Android and Chrome OS. They develop tools where they think they can improve server efficiency, web development and user devices to keep the advertising revenue flowing to Google.

      Google obviously seem room for improvement over a Linux based system. Linux was designed as a Posix/Unix replacement and the kernel is now approaching 25m lines of code and contains binary code for hardware support, it's hardly the end point of OS development. Google have developed Zircon, derived from Travis Geiselbrecht's Little Kernel to run on various devices from embedded systems upwards. Smaller, more efficient and more secure has alway been the dream of microkernels from Mach 1.0. They probably picked Little Kernel over SeL4 or Minix 3.0 because of its simplicity and the decade of experience of it being used for Geiselbrecht's NewOS and Haiku (a BeOS clone). They are using this for Fuschia, an RTOS with capability based security, that they want to multiprocess their rendering and bytecode engines.

      Fuschia might be a better replacement for Android and Chrome OS for running Google's Go/Dart/Flutter/Material Design development platform. Or it may just provide information about what will or won't work for the future.

    4. Re:NIH Syndrome by squiggleslash · · Score: 1

      This may come as a shock to you, but not everyone in the world thinks GNU/Linux is a perfect operating system, or even that Unix is the pinnacle of operating system design. If Google wants to try to create something better, that deserves applause. Even if they fail, we learn one more way how not to do it.

      --
      You are not alone. This is not normal. None of this is normal.
    5. Re:NIH Syndrome by Dwedit · · Score: 1

      According to Wikipedia, Fuchsia is supposed to be a Real Time OS, and that alone would distinguish it from any other posix-compatible OS.

  8. "Mysterious?" by Elf+M.+Sternberg · · Score: 2

    I am at a complete loss to understand how a project that is completely open source (https://fuchsia.googlesource.com/) can be considered in any way "mysterious."

    1. Re:"Mysterious?" by slack_justyb · · Score: 3, Insightful

      That's a fair statement. Strictly speaking code-wise, there's no mystery. However, I'm pretty sure that a very limited number of folks have commit access to the code on the main branch, so if those individuals are being awfully quiet about what goals they're trying to reach with their code, it can be "mysterious" as to the purpose of the code (like what problem is it trying to solve or is this just some kind of wack-a-hack project, etc...). Not knowing what the point of the code is, makes it a bit difficult to know what the next move is. Maybe they want to add POSIX compatibility, maybe not, no one knows if POSIX compatibility missing is a bug or on purpose (and yes, I'm just pulling an example out of thin air, it really could be anything). However, not knowing the point makes it hard for a new coder to jump in with the main branch. Now if they wanted to start their own derived project, totes cool there. However, imagine if their some issue with libc compatibility that someone spots, they develop a patch for it and the devs with commit access are like, "nope we did that on purpose because the goal isn't to be compat with libc" or something like that (again, just random example pulling out of thin air here). The best we can do is guess at what the devs are ultimately trying to get at here or even if there is a point to all of this or if this is just some academic dumping ground project for them.

      That's a critical thing with projects. You might have amazingly well written code, but if the communication between the programmers is crap, you're going to end up with crap. A project is more than just the codebase. A project is a multitude of things, of which, the codebase, the communication, and the leadership, among others, are major players in.

  9. Why develop your own OS? by MAXOMENOS · · Score: 4, Insightful

    It's not immediately clear exactly why Google is building a new operating system...

    Possibly to un-encumber themselves from the GPL? I note that Fuchsia's licenses are a mix of MIT, BSD, and Apache. This would potentially allow them to adapt the OS to just about any environment without having to release the source code.

    1. Re: Why develop your own OS? by Anonymous Coward · · Score: 1

      If that is the case, it probably wouldn't be the first time. I wouldn't be surprised if a huge part of Apple's motivation behind supporting LLVM and Clang was to free itself of the onerous and limiting restraints that the GPL family of licenses imposes on users (modifiers and derivers are users, too). Despite so many claims to the opposite from its supporters, the fact remains that the GPL family of licenses is very restrictive, and they do deprived users of many critical rights, including the right to modify and to distribute software without releasing the source code changes.

    2. Re: Why develop your own OS? by jareth-0205 · · Score: 0

      Despite so many claims to the opposite from its supporters, the fact remains that the GPL family of licenses is very restrictive, and they do deprived users of many critical rights, including the right to modify and to distribute software without releasing the source code changes.

      As is also mentioned by those supporters, this is the exact point. It restricts the rights of the immediate developers, to protect the rights of all developers down the line, who would not be able to further develop the code if it was closed.

      The GPL restricts your rights in a similar way to laws preventing you from murdering people. It restricts your freedom to stab me, but it is rather a good thing for me and everybody around you that you aren't allowed to do that.

    3. Re: Why develop your own OS? by Anonymous Coward · · Score: 0

      Your comment by is a perfect example of why serious companies try to distance themselves from the GPL. Both the license and its supporters hold this contradictory notion that stripping away freedom somehow grants more freedom. It's even worse when your kind compare modifying software and not releasing the changes to murder, of all things! Nonsensical comparisons like those just make you look even more out-of-touch with reality than you already look.

    4. Re:Why develop your own OS? by swillden · · Score: 1

      It's not immediately clear exactly why Google is building a new operating system...

      Possibly to un-encumber themselves from the GPL? I note that Fuchsia's licenses are a mix of MIT, BSD, and Apache. This would potentially allow them to adapt the OS to just about any environment without having to release the source code.

      Note that those are the same FOSS licenses Google uses on all of its open source projects. I wouldn't read anything into those choices.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    5. Re: Why develop your own OS? by Anonymous Coward · · Score: 0

      Sort of depends...are you a nasty, mean, horrible, evil, bad, no-good, terrible murderous person? Restricting his right to stab you may not be in the public's interest... ;-)

    6. Re:Why develop your own OS? by Misagon · · Score: 4, Insightful

      There are technical reasons also. Android under the Linux kernel does sandboxing by giving each app its own user, which I find to be a bit of a kludge.

      Fuchsia's microkernel Zircon (nee Magenta) instead uses capability-based security, in a model where Processes live in Jobs and Jobs can be nested, allowing the ones that are deeper nested having lesser privileges.
      However, Zircon has a major flaw: capabilities can not be revoked, other than by killing the whole process, or jobs.
      If I had been in charge, I would have instead chosen seL4, which has revocation, is stable on ARM and which has a formal proof of correctness (was it ten or twenty man-years of work just for the proof? I forget).
      But, yeah... seL4 is licensed under GPL. ;-P

      --
      "We mustn't be caught by surprise by our own advancing technology" -- Aldous Huxley
    7. Re:Why develop your own OS? by Anonymous Coward · · Score: 0

      It's not immediately clear exactly why Google is building a new operating system...

      Possibly to un-encumber themselves from the GPL? I note that Fuchsia's licenses are a mix of MIT, BSD, and Apache. This would potentially allow them to adapt the OS to just about any environment without having to release the source code.

      Note that those are the same FOSS licenses Google uses on all of its open source projects. I wouldn't read anything into those choices.

      Other than GPL isn’t one of them?

    8. Re: Why develop your own OS? by Anonymous Coward · · Score: 0

      If you continue the GP's analogy, a country where people are stabbing each other isn't necessarily a great place to do business long term, even if you personally have the right to stab people.

    9. Re: Why develop your own OS? by tlhIngan · · Score: 1

      I wouldn't be surprised if a huge part of Apple's motivation behind supporting LLVM and Clang was to free itself of the onerous and limiting restraints that the GPL family of licenses imposes on users (modifiers and derivers are users, too).

      That WAS the motivator for it - Apple pushed LLVM because it wasn't GPL. More specifically, it was GPLv3. Apple saw what was in the draft GPLv3 proposals, didn't like what they saw, and expended about 4-5 years of effort to bring LLVM to usability, including writing the bulk of CLang.

      Apple had no problem with the GPLv2, but GPLv3 was going to be an issue, and they migrated. Apple's last patch to GCC was to add support for Grand Central Dispatch structures. (It took 4-5 years - at first LLVM was an option, but GCC was primary, then it slowly switched over to LLVM being primary and GCC an option, and finally only LLVM).

      The other thing was there was a lot of stuff Apple couldn't do with GCC that they wanted to - because GCC wasn't modular. Things like using the GCC front end to do stuff like syntax highlighting, code flow evaluation and even syntax error analysis were impossible to do in GCC (on purpose). LLVM is more flexible and thus let Apple make XCode support partial recompilation and dynamic recompilation so your code recompiles automatically, and only the block that changed, not the entire file.

      That said, I'd say LLVM made GCC better. Using modern GCC is so much nicer now - error messages are way more useful. At the very least, competition has improved both projects and we have much better tools as a result.

    10. Re:Why develop your own OS? by swillden · · Score: 1

      It's not immediately clear exactly why Google is building a new operating system...

      Possibly to un-encumber themselves from the GPL? I note that Fuchsia's licenses are a mix of MIT, BSD, and Apache. This would potentially allow them to adapt the OS to just about any environment without having to release the source code.

      Note that those are the same FOSS licenses Google uses on all of its open source projects. I wouldn't read anything into those choices.

      Other than GPL isn’t one of them?

      Right, GPL isn't one of them. The point is that the same licenses are used by Google on lots of stuff, for which they don't hold back source code, so there's no reason to assume that the same choice of licenses indicate that Google is planning on holding back source in this case.

      For that matter, they could use the GPL without losing the ability to hold back source when they want to. The owner of GPL'd code is not required to abide by the terms of the GPL. That only applies to other people who want to use it. In many cases, even the original author is eventually constrained because of third party contributions which they don't own or have any license to other than the GPL. But Google isn't accepting third party contributions now and even if they were to do so in the future the standard Google open source contributor agreement requires that contributors grant Google an unlimited license to do anything at all with the code, so that wouldn't restrict what Google can do either.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  10. So what? by Anonymous Coward · · Score: 0

    The whole purpose of this alleged "OS" is to suck off all personal user data to Google.

  11. GPL by Anonymous Coward · · Score: 0, Interesting

    Google hates the use of the GPL by internal developers. Like most BSD projects, it's written in hate.

    https://github.com/fuchsia-mirror/fuchsia/blob/master/LICENSE

    I get why Google would do this. Why anyone else would give them development hours without a gurantee of reciprocity escapes me, as it does most developers (who side with GPL 75% of the time). People invest in codebases, they want to be able to take that investment with them - especially if they leave on poor terms.

    1. Re: GPL by Anonymous Coward · · Score: 0

      You lefties always mislabel a desire for freedom as being 'hate'. Yes, the GPL imposes some severe restrictions on freedom. That's why people who seek true freedom avoid the GPL. The GPL should not be considered a 'free' license because of how it places unreasonable and unnecessary restrictions on software devs.

    2. Re: GPL by Anonymous Coward · · Score: 0

      So you get mad at Google because they aren't providing work and propagating your OS for free for you anymore?

      You're worried Google will get up and leave you alone sitting in your sandbox with all your toys, while taking NOTHING away from you? Only a psycho or an entitled brat would yell at someone for doing that.

    3. Re: GPL by Bob+Uhl · · Score: 0

      I'm a right-winger, and I agree with the anonymous grandparent that BSD reÃmplementations of GPL projects are motivated by hate.

      BSD gives the 'freedom' to take away users' freedom. The GPL guarantees the freedom of all. It really is that simple.

    4. Re: GPL by Anonymous Coward · · Score: 0

      Hahaha, You think the GPL is right-wing? Ha! It's totally leftist. It's utterly anti-business. It's totally about the same access to the source for everyone.

      Work hard on a GPL project. Put no work into a GPL project. Either way, you have the same level of access. Sounds like socialism!

    5. Re: GPL by Megol · · Score: 1

      I hope you are trolling.

    6. Re: GPL by ArtemaOne · · Score: 1

      This assigning of left and right to everything is some of the stupidest stuff I've read on the internet all year.

    7. Re:GPL by Anonymous Coward · · Score: 0

      Like most BSD projects, it's written in hate.

      By your logic, all of the GNU stuff, including GCC, were "written in hate".

      Unix was available from AT&T, but RMS decided to reinvent that wheel because he "hated" AT&T's license terms.

  12. What big eyes you have Grandma! by jenningsthecat · · Score: 3, Interesting

    It's not immediately clear exactly why Google is building a new operating system ...

    All the better to spy on you, my dear!

    --
    'The Economy' is a giant Ponzi scheme whose most pitiable suckers are the youngest among us and the yet-unborn.
    1. Re:What big eyes you have Grandma! by Anonymous Coward · · Score: 0

      I suppose you are saying they want to more like iOS and have more unknown spying tools has under the hood?

    2. Re:What big eyes you have Grandma! by Anonymous Coward · · Score: 0

      Ohh.. how big holes you have granny Google... All the better to spy on you, my dear!
      Ohh... how big TEETH you have granny Google... All the better to EAT YOU...

  13. Successor by Anonymous Coward · · Score: 0

    some are now speculating this could be a successor to the "Andromeda" project that never materialized.

    Making this the Fuchsia project that will never materialize.

  14. A TECH site? Are you serious? by Anonymous Coward · · Score: 0

    This is a site for MRAs and Trump-lovers who occasionally talk about Linux because it makes them feel all smug and superior.

    Posting anonymously because I'm one of the few that don't fit into that category and I want to keep my karma.

  15. Hopefully, innovation by Camembert · · Score: 1

    âoeIt's not immediately clear exactly why Google is building a new operating system...â

    Unix is more than 40 years old. Granted, it works well on computers of different size levels and below the hood on both android and iOS devices.
    But still, it is conceptually old, certainly by IT evolution standards.
    I can imagine that a company with the funds and intellectual workforce like Google would be capable of innovating operating system principles taking into account the advances in academic research.
    It wouldnâ(TM)t surprise me if a team of Apple engineers were also, and obviously more secretively, working on a next generation operating system as well.

  16. We can't predict what they will do next by InterGuru · · Score: 1

    Unforeseeable Fuchsia!

  17. Jostling for position by Anonymous Coward · · Score: 0

    Pichai pushes ChromeOS as the mainstream and that flops. I could write reams about how crap Android is on Chromebooks is, but in essence it runs Android badly and removes the big 'locked down' feature that gave ChromeOS its niche.

    Pichai also fragments Android, the latest Android that can't run most Android apps being Android Go.

    So they can see the opening that's there. As long as Pichai is in that seat, Android for Desktops will be led by Samsung Dex, not from within Google.

    So if you were a bored undervalued tech in Google, wouldn't your side project be an OS? It's your best chance of getting a star role. I don't think there is any big plan there, I think its people laying out their wares to the Google board.

  18. Re: An opening for the competition by Hognoxious · · Score: 0

    among many other marketing successes. Google is the premiere marketing company today.

    FTFY

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  19. As a professional System SW Engineer by OrangeTide · · Score: 1

    I can tell you it takes a very short time to port a simple kernel/microkernel/nanokernel to a new architecture. Some of the kernels we deal with in the industry have been brought over to entirely new CPU architectures as a proof of concept over a weekend. So that someone at Google got a hankering for some porting work is not surprising, but it's not likely a terrible amount of effort either. (still cool work though)

    --
    “Common sense is not so common.” — Voltaire
  20. Re:A TECH site? Are you serious? by Anonymous Coward · · Score: 0

    You think here is bad? The worst of them left for Soylent News.

  21. Re:A TECH site? Are you serious? by KozmoStevnNaut · · Score: 1

    Who cares about karma on some random past-its-prime "news" site?

    --
    Eat the rich.
  22. Pronunced - "Fucks Ya" by Anonymous Coward · · Score: 0

    Just wanted to clear up how to pronounce Fuchsia. Sounds like "Fucks Ya"...because it does.

  23. Re: An opening for the competition by ArmoredDragon · · Score: 1

    No, the companies with the most marketing successes include Apple and Bose. Google isn't much of a marketing company, nor are they anything special when it comes to advertising (Apple and Bose are way ahead of them here.) Google's success is being a master at matching advertisers with their target audience, and they sell a TON of ad space.

  24. Re: An opening for the competition by Hognoxious · · Score: 1

    Google got search right (or good enough) at the time there was no incumbent. Alta Vista dropped the ball for no apparent reason and it landed at Google's feet.

    Everything else they've done had been mediocre at best. That or they bought it in, *then* made it mediocre after optionally fucking the UI up. If by pure dumb luck some renegade skunk works cowboy lunchtime side project makes something even half useful they discontinue it.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."