17 ms·
Fuchsia: Google's modular, capability-based, non-Unix operating system
- abrowne 9y agoThe "Web runtime" is under the header "Backwards compatibility".
- cheez 9y agoWhy?
- orf 9y agoWhy not? Have we reached the peak OS development, and any more is pointless?
- trimbo 9y agoI think peak OS development was in the 70s and 80s. Every hardware vendor also had their own OS, or several. The System V OSes were just different enough to be annoying. To name a few: UNICOS, NeXTStep, HP-UX, RSTS, ULTRIX, VMS, AIX, SunOS, Solaris, IRIX, A/UX, MacOS, ProDOS, Amiga OS.
- rmusial 9y agoLinux isn't capabilities based, or real time by default. Google likes permissive licenses. Android, while good, was a knee-jerk by Google in reaction to the iPhone. If you've got the resources of Google, why not try to build something in house that scratches some long standing itches and at the same time get ownership over the OS that could power everything from your phones to laptops?
- tziki 9y agoAndroid was in development far before iPhone was released.
- vvanders 9y agoYeah, and Danger was doing a lot of interesting stuff in the space as well. They were the first to do push based email and IM in a context outside of business AFAIK.
- drewvolpe 9y agoThe original version of Android looked like and worked like a Blackberry: small screen with a physical keyboard and a D pad for navigation (no touch control). When the iPhone was announced in 2007, they realized that on-screen keyboards and multi-touch control were the future, so they did a complete redesign, moving to an interface similar to the iPhone. Here's a quote from one of their engineers talking about the iPhone announcement: “As a consumer I was blown away. I wanted [an iPhone] immediately. But as a Google engineer I thought ‘We’re going to have to start over’” Chris DeSalvo said. “What we had suddenly looked so… nineties. It’s just one of those things that are obvious when you see it.” http://bgr.com/2013/12/19/original-iphone-android-story/ http://bgr.com/2013/12/19/original-iphone-android-story/
- blinkingled 9y agoNothing to do with OP's point of Android being based on Linux even before the iPhone. [Every time this story is told, I like to remind - note how fast Google were able to pivot / adapt when Microsoft with their crazy resources and Engineering might took way longer. (Even beyond that MS had to change the way apps were developed for WP.) Fact is Google/Danger/Android were in a fundamentally good position mobile OS design wise way before the iPhone. After the iPhone - they looked at the possibilities of multi touch soft keyboard UI and were able to get there and surpass fairly fast.]
- addicted 9y agoTo be fair Google knew about the iPhone well before Microsoft did (they worked closely with Apple in the beginning for Maps and search). But even adjusting for that it took MS 3-4 years after the iPhone to just get Windows Phone 7 out, and that was also clearly a rushed release, because they had to throw everything out for Windows Phone 8.
- alecco 9y agoControl.
- Lutia 9y ago> Why? Not having to deal with Linux's refusal of maintaining a stable driver API and ABI for a start. The number one reason that stops Android from getting updates on smartphones is that hardware manufacturers don't want the burden of constantly making small changes to their proprietary drivers to follow new linux kernel changes, something that they don't have to worry about when they make drivers for, say, Windows PCs. Even Google's own phones, like the Nexus and Pixel, are stuck because of this. They receive updates faster than non-Google phones, but they do not receive more than 2 years of feature updates (with an additional year of security updates courtesy of Google backporting fixes from newer android builds to the older kernel). Fuchsia is not going to be burdened by Linux kernel dev policies of constantly breaking APIs and their requirement for driver developers to open source their stuff, obey the kernel coding preferences (like when they rejected AMD's driver because of the HAL) to get them mainlined so that they can finally be kept in a maintained state.
- catern 9y ago>Fuchsia is not going to be burdened by Linux kernel dev policies of constantly breaking APIs and their requirement for driver developers to open source their stuff, obey the kernel coding preferences (like when they rejected AMD's driver because of the HAL) to get them mainlined so that they can finally be kept in a maintained state. And as a result, its drivers will be far lower quality and much less stable, and the system as a whole will pay the complexity cost of working around the awful code that hardware vendors churn out.
- quotemstr 9y ago> And as a result, its drivers will be far lower quality and much less stable I don't buy it. Windows provides stable driver ABIs and works just fine. A lot of the changes to the Linux driver API are gratuitous, and isolating driver development from the whims of the core won't actually hurt. If anything, a stable ABI will help, since a smaller, well-defined boundary between the kernel core and drivers allows for things like Vulkan-like validation layers, better debugging, better sandboxing, and even transparent thunking to userspace. Will some drivers be shitty? Of course. But many drivers won't be, and drivers will be less shitty overall when they can spend more time on being good drivers and less time dealing with GFP_FOOBAR becoming GFP_BARFOO. Conventional wisdom is that backward binary compatibility i some huge unreasonable burden. This conventional wisdom is wrong; if anything, maintaining a stable ABI imposes some discipline that focuses development effort and that forces you to modularize your system.
- filereaper 9y agoI'm curious to hear about the design principles going into Fuchsia... ie Unix tried out X, but that inturn runs into issues Y and Z down the line. i.e the "why" behind the design they've chosen.
- nl 9y agoUnix tried out X For a moment there I thought you meant the X Windowing system.
- gigatexal 9y agoIf anyone was going to reinvent an OS I’d like google to do it. They’re capable and have the cash to do it. I do think have this in conjunction with buying HTC (rumored) could be them trying to iPhone and their lineup by owning both the software (via fuschia) and the hardware.
- norswap 9y agoGoogle can't get Gmail to sort mail properly. Amongst a thousand of small grievances I have. That may seem quite irrelevant, but if I'd like someone to reinvent the OS, I'd like it to be people that have taken a stance in favour of stable, simple, straightforward software (the people behind Pinboard, Tarsnap; djb... just to name a few).
- lamlam 9y agoI've never had any issues sorting mail in gmail. I'm curious what specific action causes mis-sorting.
- norswap 9y agoBasically, in some views the sorting is by the first message in the thread, while in other views it is by the last message (that last one makes more sense to me). Even more surprisingly, Inbox (by Google) sorts everything by last message (last time I checked, which was a long time ago).
- manigandham 9y agoYou can't sort by "From" at all.
- smallcompanies 9y agoIt seems like the software you mentioned does well because they are so small. I'm not sure a team similarly small could produce a modern OS that addresses the needs of generic phones (in the sense of they are truly incredibly complex oses, not in the sense of running on arbitrary phones). Notably, small teams can dictate priorities that don't scale at the level of tens of thousands of engineers.
- deleted 9y ago[deleted]
- baybal2 9y agoIt is not GPL, therefore it is bad. If their main point was to get rid of GPL in kernel, and low level userspace, their main point is bad.
- systems 9y agowhy does the wikipedia page have Go, Rust, Python and Kotlin in the languages list Fuchsia is written in?
- topspin 9y agoThat seems like a stretch. When you look at the Fuchsia OS repositories in Github and select these by language the overwhelming bulk are C++. Regarding the languages you cite: there are some non-trivial parts in Go; the Fuchsia package manager, for instance. There are several bindings to certain key parts of the OS provided for Rust, but no actual Rust components that I can see. Python is used for some build and packaging utility type stuff. Kotlin is provided with one binding library with four whole commits. Regarding two others mentioned in wikipedia; Dart is actually more prominent than Go, Python, Rust and Kotlin combined. C has lots of binding libraries, but only a pair of boot loaders appear to be core components, plus a fortune stub.
- bitmapbrother 9y agoThe Fuchsia OS network stack is built in Go.
- kyrra 9y agoYou can poke around their github mirror and filter project by language, for example Go[0]. pm, wlan, thinfs, and netstack looks like some decent size components written in Go. Rust and Kotlin looks mainly like bindings at this point (no real core parts yet). Python has 'build' and 'scripts', which look like tools useful when doing dev on Fuschia. [0] https://github.com/fuchsia-mirror?utf8=%E2%9C%93&q=&type=source&language=go https://github.com/fuchsia-mirror?utf8=%E2%9C%93&q=&type=sou...
- Sir_Cmpwn 9y agoEach time this comes across my feed, there's a brief period of excitement - "oh yeah, we're getting a new not-Unix microkernel backed by a major company!" A few moments later I remember that it's being written in C++ and is basically the evolution of Chrome OS and the mood dampens. I'm still be waiting for the next truly innovative OS to show up and poise itself to become ubiquitous. Unfortunately I don't have much faith in Fuschia, especially after poking around in Chromium. In the spirit of HN though this comment basically guarantees its success, right?
- pstuart 9y agoWhat language would satisfy you?
- Sir_Cmpwn 9y agoJust C. Rust has a lot of problems for serious low level work imo and suffers from a lot of the same classes of problems C++ does, and there aren't many other candidates. A simple microkernel should be fairly straightforward to write in C without any big security concerns, especially in the hands of a multi-billion dollar company. You offload most of the security work to the architecture.
- bluejekyll 9y ago> Rust has a lot of problems for serious low level work Could expand on where it suffers? I've been playing around with Rust in the embedded space (nothing serious at all); I find it to be as elegant in a nonstd situation as it is in standard high level app development. > and suffers from a lot of the same classes of problems C++ does, What are those classes of problems? C++ never offered a safe alternative to C, but did offer some eases of use and stronger typing over C. Rust on the other hand has a huge amount to offer over C. At no point in my Rust work do I ever wish I was working with C, quite the contrary. But I like strongly typed languages, Rust is definitely not for those that dislike types.
- Sir_Cmpwn 9y ago
- GorgeRonde 9y agoWhy everytime a "new OS" comes around it uses the good old fashioned command line with the GNU stack ?
- X86BSD 9y agoNot every new OS does. The ones that do are using the GNU stack, at least initially because they are there and it saves time. Even then down the road some purge GNU from their OS in favor of better utils, more liberal licensed code, etc.
- lobster_johnson 9y agoI'm pretty excited about Fuchsia. Just the fact that, if successful, it will be the first true production-quality general-purpose microkernel-based OS in the mainstream. (QNX and Minix are of course also successful microkernels, but both are pretty niche at the moment; are there any others?) The design also seems extremely sensible and modern: Everything is namespaced and sandboxed (there's no default "/"), everything is an "object" (sounds similar to Plan 9's file descriptors), capabilities from the ground up, standard RPC between OS components (FIDL, similar to COM or XPC), built-in package management (looks like apps aren't globally installed by unpacking archives, but rather they're run directly from packages, and the process gets the archive file system mounted in its namespace), etc. While Google seems to be aiming for phones, I wouldn't surprised if this ends up as an option on Google Cloud Platform in a few years' time.
- fiddlerwoaroof 9y agoWasn't the XNU kernel a microkernel originally?
- lobster_johnson 9y agoXNU uses a heavily modified Mach 3.0, which is a microkernel, but it doesn't use it as a microkernel, and never has. In XNU, things like file systems, graphics and device drivers are all running in kernel mode, in the same address space as the kernel. The Windows kernel has the same design -- it's designed as a microkernel, with separate modules internally that communicate via a form of IPC, but everything is running in one process (as opposed to a real microkernel architecture where file systems etc. are userland processes). With XNU, Apple forked Mach 3.0 and have been making a lot of changes to it over the years, even though Mach itself has progressed since then. On the other hand, XNU inherited Mach's high syscall overhead (considerably higher than Linux), and to my knowledge Apple has moved a lot of stuff into ordinary syscalls rather than Mach messages to remove this overhead. Edit: Interestingly, around the time before Leopard, when Darwin was still a thing, there was a research project called Darbat [1] that tried to supplant parts of Mach with L4, a more modern microkernel, and actually run XNU as a userland process on top of it. Unfortunately, nothing came of that project. [1] https://arstechnica.com/staff/2006/06/4407/ https://arstechnica.com/staff/2006/06/4407/
- Kabie 9y agoThey renamed the kernel(Magenta) to Zircon.
- 0xbear 9y agoTheir main problem is not the kernel. It’s their application APIs. What a clusterfuck that is in Android. And now with tens of billions of LOCs written for it they’re stuck with it forever.
- HillaryBriss 9y agoi mostly agree. as a mere mortal android app programmer, i feel a significant amount of pain when i build apps using the android SDK and the standard set of tools. there's a lot of weirdness, confusion, unexpected behavior, anemic documentation and irregularity. (it's getting better, but not fast.) i guess Google's Fuchsia push is motivated by some other, internal concerns.
- rossy 9y agoThis seems good and bad. The prospect of a new, modern operating system is exciting. The system call interface is sensible and it follows modern security best practices (eg. deny-by-default.) One practical disadvantage compared to Linux is that it's not GPL, so if Google uses it to make a mainstream mobile phone operating system, other vendors won't be compelled to release their kernel sources like they are with Android today, which means a Fuchsia equivalent to LineageOS might not support as many devices. Also, capability-based security is fine as long as there's some way for the owner of the device to acquire all capabilities. If there is not, it's fundamentally anti-user, since it's treating the user as an adversary. Since most Android devices require aftermarket modifications to get root access, I'm not too hopeful about Fuchsia. If these bullet points are anything to go by and DRM and verified boot are first-class features, it's likely that Fuchsia will have built-in mechanisms that prevent the user from copying protected video content, so it's unlikely that the average Fuchsia powered device would grant the user full privileges.
- gonyea 9y ago> it's fundamentally anti-user I don’t get this sentiment at all. The vast majority of users don’t know what root access is, let alone care about it.
- rossy 9y agoWhether the user knows it or not, there is still software running on the device that is working in the interests of the vendor and/or the DRMed content creator and against the interests of the user. Yes, most users don't care, but some do. If you were the seller of a hypothetical restricted Fuchsia device, you might not lose any sleep over the users that care. As the potential buyer of the device, I will take user freedom into consideration and I will criticise the device if it's not up to my standards. Also, users don't care about these restrictions until they do. The user might be completely unaware that there are restrictions on what they can do with the device before they decide to install something like a system-wide ad-blocker (which are becoming more popular) or maybe an app that can download YouTube videos.
- 9y ago
- 2_listerine_pls 9y agoIs it Linux?
- omarforgotpwd 9y agoSeems cool that you can pass “handles” to resources like network connections between processes. That could definitely make some server software easier to architect.
- naasking 9y agoYup, everything old is new again. This was part of one of the first capability operating systems in widespread operation back in the 70s: KeyKOS.
- nopacience 9y agofirst they created google, then they created gmail. then orkut. then android. when will google toilet arrive ? trust them for everything
- romanovcode 9y agoAndroid will be running on this OS.
- TheAceOfHearts 9y agoDefinitely suggest reading through their docs, it's fascinating. One of the features I'm most excited about is storage management. From "What is ledger?" [0]: > Each data store is transparently synchronized across devices of its user through a [cloud provider]. Any data operations are made offline-first with no coordination with the cloud. If concurrent modifications result in a data conflict, the conflict is resolved using an app-configurable merge policy. I'll note that although they use Firebase as the sync provider, it should be fully possible to host your own if you wish to avoid the cloud. Keeping stuff in sync can be a huge pain sometimes, especially when you're just dealing with scattered files. I like having this functionality as part of the core system, and getting developers to handle our multi-device world. The Ledger design docs are worth reading, they're short and approachable. Architecture [1] explains how it's implemented, and Conflict Resolution [2] covers how to handle when things go wrong. [0] https://fuchsia.googlesource.com/ledger/#what-is-ledger https://fuchsia.googlesource.com/ledger/#what-is-ledger [1] https://fuchsia.googlesource.com/ledger/+/HEAD/docs/architecture.md https://fuchsia.googlesource.com/ledger/+/HEAD/docs/architec... [2] https://fuchsia.googlesource.com/ledger/+/HEAD/docs/conflict_resolution.md https://fuchsia.googlesource.com/ledger/+/HEAD/docs/conflict...
- davemp 9y agoJudging from google's track record with android, chrome, and youtube, I'm not very excited for this project. As much as I would love some innovation in the OS world, I find myself hoping that this system does not catch on. Google has not proven themselves to be a developer/enthusiast friendly company. It feels like they look down on the rest of the world while locking systems behind restrictive(cumbersome) APIs to protect the unenlightened from themselves. Maybe that design philosophy is okay for services/apps but it has no place at the system level IMO. Who knows maybe the fuchsia team doesn't share that philosophy, but I doubt it.