I'm still not clear on what fuchsia is trying to be - or more specifically, why is Google developing it. What is the end goal here, from a business perspective?
It’s already running on some of their embedded devices, such as google home. A capability based OS with a micro kernel sounds great to me. Things like the networking stack can run in user space, and be written in memory safe languages like Rust. An OS that “can’t” get viruses or be hacked sounds pretty desirable. Cynically it makes things like “jail breaking” a google home much more difficult.
Expanding Fuchsia's open source model
51–60 of 334 posts
Re: Expanding Fuchsia's open source model
#52Earlier quoted context omitted.
As a principal software engineer that works on Fuchsia, I can assure you that the project does not exist solely to retain me. :)
Congrats on the promo! It didn't retain me (though I didn't get promoted to Principal, so maybe I don't count) but I did enjoy working on Fuchsia. Nice to see much of the syscall design seems to have survived.
Re: Expanding Fuchsia's open source model
#53Sundar, do you think we will believe you? Google will bait and switch you again, like it did with Android.
Can you elaborate on Android part?
Re: Expanding Fuchsia's open source model
#54Earlier quoted context omitted.
You are describing the difference between the GPL and BSD-like licenses. You have not said anything about the difference between a BSD-like license with copyright remaining with the contributors versus BSD-like license with copyright assigned to Google.
Well if I have the copyright I can straight up sell software based upon it without telling people you made it. Or I can release your code or derivatives of it under a different license while privately selling it under other licenses for profit. If these things don't bother you, then feel free to contribute. In fact, what I'm trying to understand exactly is if I assume that you are correct that there is no difference,…
The difference isn't relevant 99% of the time, but it comes up if the maintainership of a work tries to re-license the work. Works without assigned ownership cannot practically be re-licensed, as you'd have to get individual consent from all owning parties.
This came up a lot when GPLv3 was introduced — many projects wanted to migrate from GPLv2 to GPLv3, but couldn't, because they never acquired legal ownership of contributed code, and so didn't have the right to re-license the contributors' code.
Re: Expanding Fuchsia's open source model
#55I'm still not clear on what fuchsia is trying to be - or more specifically, why is Google developing it. What is the end goal here, from a business perspective?
Re: Expanding Fuchsia's open source model
#56So maybe open source, [mostly] closed ecosystem? Add a bunch of Spyware from Google and get every app maker to add a dependency to Google services and they are golden for the collection of data on all your "smart" things Sorry/not sorry for the cynicism; I feel it is warranted given what "open source" means on Android. Google talking like they have noble open source ambitions means nothing. They have a lot of amends…
If they do the same with Fuschia, they'd better make it closed sources then.
Re: Expanding Fuchsia's open source model
#57Earlier quoted context omitted.
Welcome to the world of Building Large Google Projects. This is somewhat painful in the Android and Dart/Flutter world. I haven't tried building Chromium yet but I'm sure it's just as complex.
Yeah, I've tried building Chromium on my own before. Chromium's build process is so inscrutable and changes so often that several Googlers I've talked to have said you can't really do it without handholding from another Googler in-the-know.
git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git
Add it to your PATH fetch --nohooks chromium && cd src
./build/install-build-deps.sh
gclient runhooks
gn gen out/Default
autoninja -C out/Default chrome
Congrats, you just built Chromium. Is it a different build process? Sure. But it sure isn't inscrutable, and they've been using this system for a while now.Re: Expanding Fuchsia's open source model
#58I've heard Fuchsia referred to as a "principal engineer retention project" at Google. I'd be curious to know if others have heard the same.
As a principal software engineer that works on Fuchsia, I can assure you that the project does not exist solely to retain me. :)
Re: Expanding Fuchsia's open source model
#59So maybe open source, [mostly] closed ecosystem? Add a bunch of Spyware from Google and get every app maker to add a dependency to Google services and they are golden for the collection of data on all your "smart" things Sorry/not sorry for the cynicism; I feel it is warranted given what "open source" means on Android. Google talking like they have noble open source ambitions means nothing. They have a lot of amends…
You cannot expect they would not do the same bait and switch as with android without a legally binding pledge.
And even then, I bet Sundar will try to wiggle around it.
There is a clear repeating pattern in what he does:
"Google does not store geographic information of AGPS requests" — It did.
"Google will never attempt to block adblock from Android store" — It did.
"Google never shares your cellphone network data" — It did!
Clearly, he lies, and does it very intentionally.