Superposition of EigenelliesNov 25, 2018
ME[learning about fuchsia for the first time]: oh god I hope that's not horrible
ME [hearing about fuchsia again a few months later]: it's gonna be horrible isn't it
ME [hearing more about fuchsia about a year later]: fucking bury it in the desert, holy shit
Show threadSuperposition of EigenelliesNov 25, 2018
How I would be looking ahead if I were Google:
- The biggest flaw in Android is that it's hackable and contains privacy features that make it possible to cripple the spyware in it
- The "look but don't touch" open-source model works great, let's clamp down even harder on it
- Why don't we try packaging most of the system in nice modular binary blobs, so that things like OEM drivers, platform-specific UIs, and apps are easy to install but impossible to modify
- Also how about it tracks all of its activity at the kernel level and reports it directly to us, and you can't disable that without refusing network access to the kernel altogether
- Sure, folks will try to fork it, but that won't go well for them if the OEM driver blobs are illegal to distribute and will only work with official signed kernels
Show threadSuperposition of EigenelliesNov 25, 2018
And better yet, they don't even need to hire any copyright police to make sure you don't accidentally try to hack the driver blobs into working on an unapproved kernel - the current Android communities will handle that for them, for free.
Show threadSuperposition of EigenelliesNov 25, 2018
Presumably there will be a few "community firmware blobs" available for purchase for $25-$50 to allow you to use a hacked phone, meaning that
A) no one will bother buying those, meaning that Google will be happy
B) anyone producing free versions of those will be labeled as an evil pirate and summarily exiled
Show threadSuperposition of EigenelliesNov 25, 2018
seriously though, we're absolutely fucked regarding OEM drivers and Fuchsia.
- Zircon is MIT licensed, meaning nobody has to open-source their modifications (e.g. kernel drivers!) like they do for Linux
- Vendors love to keep their firmware and drivers as locked down as possible because semiconductor IP is fuck fuck fuck fuck fuck
- Zircon is being marketed as a "microkernel" meaning that it will probably contain few or no generic drivers of its own
- We'll still have a little luck with RE, but RE is much harder than just working with published source
Basically I kinda feel like we have until whenever Fuchsia takes over the market to get FOSS hardware going, because we're really going to need it after that
Show threadBrian Swetland

@diodelass For your consideration:
1. Presently all Zircon/Fuchsia drivers are open source except for the guts of the Mali GPU driver. The Intel GPU driver is open source, for example.
2. This is no different than many Android situations where the vendor GPU userspace library is a closed component.
3. Nobody has to release source != nobody will. Google certainly is and others are strongly encouraged to do so.
4. Linux's death seems unlikely to me.

(SW Engineer, not GOOG PR)

Nov 25, 2018 at 7:10pmWeb
Show threadSuperposition of EigenelliesNov 25, 2018
@swetland
1. Encouraging, but I'm still waiting to see if it stays that way as Fuchsia develops and hits the market.
2. Yeah, and Android devices are already hellish to develop for.
3. Again, true, but I'm still expecting there to be some serious roadblock to having Fuchsia be hackable on the majority of devices. IIRC we thought Android would be hackable too, and nowadays almost everything has a locked bootloader and isn't rootable.
I appreciate your input. I'd really like it if this didn't turn out to be a nightmare, so I hope you're right.
Show threadBrian SwetlandNov 25, 2018

@diodelass I deeply appreciate the wariness about Google.

All I can say is there is a team of people who are very committed to open source and open platforms working on Fuchsia and I believe the engineering team would push back hard against the dystopian future of locked down horrible vendor blob drivers.

There's a lot of inspiration from the Chrome and CrOS folks here too, who are a very committed to open-source bunch.

I sincerely hope we prove your worries unfounded.

Show threadOndřej PokornýNov 25, 2018
@swetland @diodelass I was just going to respond that Chrome OS, not Android, should be setting the bar here.
Show threadBikey BoiDec 1, 2018

@swetland The team your interacting with might be very committed to open source, but without the teeth the GPL provides we're stuck with driverless, tivoized hardware, leaving end users with no ability to modify their OS or the bundled shovelware atop it.

Chipset manufacturers do not often release their code willingly, and making it easier to have black box drivers will only feed this issue. Google has not supported open driver projects other than leveraging their work AFAICT.

Show threadBrian SwetlandNov 25, 2018

@diodelass I know there are all kinds of theories about MIT/BSD and evil closed source, but, truly, I believe that's a distraction.

The team working on Zircon/Fuchsia, committed to open source, that has been developing the bulk of the system (minus product-centric apps & UI) fully in the open, for the past year and a half. Code-reviews and code. Live on fuchsia-review.googlesource.com / fuchsia.googlesource.com.

Compare vs Android "throw it all over the wall when it's done"

Show threadBrian SwetlandNov 25, 2018

@diodelass Speaking only for myself, as I do not (and do not wish to) speak for my Corporate Overlords:

I didn't come *back* to Google to work on an operating system that I felt would be *less* open source than Android.

I spent the first year of Android fighting for Linux-on-the-metal, instead of Linux-virtualized-under-L4 or other insanity vendors proposed.

I spent my tenure on the Android systems team ensuring that every Linux driver we shipped was open source.