1. 15
  1. 10

    How many connections to google it does while compiling/booting?

    1. 11

      It’s a shame Google can’t run open-source projects. Fuchsia looks like one of the more interesting operating systems but as long as Google has complete control over what goes in and no open governance it’s not something I’d be interested in contributing to.

      1. 11

        To be fair to Google - they’re doing work in the open that other companies would do privately. While they say they welcome contributions they’re not (AFAIK) pretending that the governance is anything it’s not. On their governance page, “Google steers the direction of Fuchsia and makes platform decisions related to Fuchsia” – honest if not the Platonic ideal of FOSS governance.

        To put it another way - they’re not aiming for something like the Linux kernel. They know how to run that kind of project, I’m sure, but the trade-off would be to (potentially) sacrifice their product roadmap for a more egalitarian governance.

        Given that they seem to have some product goals in mind, it’s not surprising or wrong for them to take the approach they’re taking so long as they’re honest about that. At a later date they may decide the goals for the project require a more inclusive model.

        If the road to Hell is paved with good intentions, the road to disappointment is likely paved with the expectation that single-vendor initiatives like this will be structured altruistically.

        1. 6

          The governance model is pretty similar to Rust’s in terms of transparency: https://fuchsia.dev/fuchsia-src/contribute/governance/rfcs

          Imperfect in that curreny almost all development is done by Google employees, but that’s a known bug. But (to evolve the animal metaphors) there’s a chicken and egg issue here. Without significant external contributions it’s hard for external contributors to have a significant impact on major technical decisions.

          This same issue exists for other OSes like Debian, FreeBSD, etc - it’s the major contributors that have the biggest decision making impact. Fuchsia has the disadvantage that it’s been bootstrapped by a company so most of the contributors, initially, work for a single company.

          I’m optimistic that over time the diversity of contributors will improve to match that of other projects.

          1. 4

            A real shame indeed. Its design decisions seem very interesting.

            1. 1

              yeah I’d bet the moment they have what they wanted it’ll be closed down, because this is ultimately the everything-owned without GPL -OS for google

            2. 7

              Probably zero. Or if you’re using 8.8.8.8 for your DNS probably less than Windows or macOS.

              1. 5

                They all start like this, but at the end it will be another chrome.

                1. 5

                  Co-developed with companies as diverse as Opera, Brave, Microsoft and Igalia, as well as many independent individuals? As a Fuchsia developer that’s a future I aspire to.

                  1. 13

                    Chrome, which refused to accept FreeBSD patches with a community willing to support them because of the maintenance burden relative to market share, yet, accepted Fuchsia patches passing the same maintenance burden on to the rest of the contributors, in spite of an even smaller market share? If I were an antitrust regulator looking at Google, their management of the Chromium project is one of the first places that I’d look. Good luck building an Android competitor if you’re not Google: you need Google to accept your patches upstream to be able to support the dominant web browser. Not, in my mind, a great example of Google running an inclusive open source project.

                    1. 6

                      It’s not just about whose labor goes into the project, but about who decides the project’s roadmap. That said, maybe it’s about time to get the capability-security community interested in forking Fuchsia for our own needs.

                      1. 3

                        You should be more worried about the “goma is required to build Chrome in under 5 hours” future, in my opinion.

                        1. 0

                          Keep aspiring on google salary. It would be good to disclose conflict of interest btw.

                          1. 11

                            I mentioned that I’m a Fuchsia developer. I’m not sure what my conflict of interest here is. I’m interested in promoting user freedom by working on open source software across the stack and have managed to find people to pay me to do that some of the time, though generally less than I would have made had I focused on monetary reward rather than the impact of my work.

                    2. 5

                      The website doesn’t have working CSS without allowing gstatic.com, so I’d guess at least one?

                      1. 1

                        /me clutches pearls

                    3. 7

                      So, what’s it like running Fuchsia on bare metal? That’s what I was hoping the article was about.

                      1. 2

                        Yes, I would much rather hear about what it’s like to install and run Fuchsia, than debate its ideological purity. (But then, I’m one of those blackguards who runs a corporate closed-source OS.) Has anyone actually sullied themselves?

                        1. 1

                          I think this can be used on bare metal with “Intel NUC” hardware, but that seems pretty limiting.