1. 36

  2. 8

    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.

    Well, I’m glad to see they’re still open-sourcing parts of it. Does anyone know if there’s going to be a proprietary layer à la Google Play Services?

    1. 19

      Does anyone know if there’s going to be a proprietary layer à la Google Play Services?

      Google makes billions in revenue on proprietary layers they add into almost everything. We can default on saying yes until they prove otherwise. It’s even acceptable to me so long as I can turn it off. Let them get paid for their work if people are willing to be spied on.

      1. [Comment removed by author]

        1. 2

          The main risk is open part remains diluted in terms of features. Thats fine to me long as it’s useful, extendable, and/or forkable. Best model I see is in enterprise where the good stuff can be free and the hard stuff worth extra money is enterprise integrations consumers don’t even care about. Active Directory integration on a web server comes to mind.

      2. 6

        Not really bothered by the proprietary layers, but more that hardware vendors no longer will be creating GPL drivers for their SoC’s.

        The small diversity that LineageOS and the like brought to the things we carry around with us everywhere and use the most, now will start to be completely closed off.

        Having the base OS opensource’d is quite useless to you and I without the drivers too.

        1. 4

          Maybe that will focus more energy into community-supported hardware like the Pyra and Neo900. IMO Android phones have never been a suitable platform for freedom/user control in the mobile space.

          1. 2

            But most SoC drivers are binary blobs, aren’t they? Problem is that the in-kernel interfaces are not stable. AFAIK they want to have stable ABI for drivers. So probably if you would recompile the base open-source OS yourself you should be able to use binary drivers just fine. Of course I can imagine a couple of scenarios where it is blocked by some code signing layers or something, but it could be done already.

            It would be really nice to have open-source drivers, but I would argue that it’s easier to open-source your driver if there is a stable kernel interface for drivers. But I’m disillusioned - open source drivers will happen only for a few moderately popular devices.

          2. 3

            I have a guess

          3. 4

            Not surprising, although it does seem like diminishing returns at this point (unless you count nixing any potential lawsuits, in which case it seems like a big win).

            The thing that caught my eye about this, though, is that the entire UI as well as apps are being built using something new called Flutter: https://flutter.io/. I guess Google thinks that cross-platform solutions like React Native, Cordova, etc. are the way forward because that’s what they’ve decided to make here. Also, Flutter is built on Dart, which up to now 1) I thought was just a way to write fancy JavaScript à la TypeScript and 2) I didn’t think was actually being used for anything. Seems pretty neat.

            1. 2

              Dart was originally built for a VM! My understanding is that they originally compiled to JS so that other browsers could run Dart. I’m not sure if that officially is the stance anymore–I’m guessing not?

              1. 2

                The VM will not be going into Chrome, but they’re improving the compilation to JS and the language itself quite a bit. The VM will remain supported, just not bundled with a browser. Source: I use Dart at work :-)

              2. 1

                I didn’t think was actually being used for anything.

                According to them, Google rewrote basically their entire ad platform in Dart.

              3. 2

                I’m sad that we are still building new OSes with C. :-(

                1. 7

                  If it makes you feel better, half the kernel is in C++?


                  1. 14

                    Now that makes me sad.

                    1. 2

                      Also theres some Rust in there (specifically xi-editor, the editing backend for all UI). I don’t think it is in the kernel though. Could be wrong.

                    2. 6


                      1. 3

                        About a billion security problems over the last two decades.

                        1. 2

                          Sorry, not taking the bait. Nice try. :-)

                      2. 3

                        My understanding from an article I read awhile ago is that a lot of the lower-level code will be Go.

                        1. 3

                          The network stack is in go. Rust support is getting there.

                        2. 2

                          What’s the alternative?

                          1. 1

                            I didn’t say I had an alternative. I’m sad it’s still the only viable choice.

                          1. 1

                            Or is that not a thing anymore?

                            No, not on that kind of devices. We’re specializing into “computers for creators, interactive displays for consumers” world. Which is okay by me, as long as I can buy a computer :-)