I find it hard to believe that 8+ years of APIs and OS level code would be abandoned just like that, especially given the scale of Android. If this ever happens, it would probably be an extremely slow, well thought out (hopefully), well documented (also hopefully) rollout.
They've already replaced Dalvik with ART for bytecode and it was mostly transparent from what I understood. But popping up with a completely new platform API without any backwards compatibility would be very bold and risky. There would have to be a good compatibility story there. Also there is talk in the article about a POSIX layer. Now that's easier said than done. But it is Google we are talking about so they cert…
“Proof” that Fuchsia will replace Linux for Google
31–40 of 59 posts
Re: “Proof” that Fuchsia will replace Linux for Google
#32I thought google would do something like this. They didn't want to fully embrace linux so they locked all the freedom of linux away behind restrictrions in android until they had a replacement and now they are going to try to drop gnu+linux anything GPL they can... The new kernel is MIT/BSD... Welcome to Tivoization all over again. I get the need for a better kernel, the gnu+linux kernel is out of control at over 14m…
If Google builds this kernel from the ground up and chooses to license it MIT, how is any binary derived from that "built on the backs of the FOSS community?"
Re: “Proof” that Fuchsia will replace Linux for Google
#33Earlier quoted context omitted.
That's what I'm saying :) An (extremely) gradual phase-out of the Android API.
I'm not sure the API can ever really be phased out due to the vast amount of legacy apps and libraries. Besides I'm sure a lot of developers wouldn't be happy that their domain knowledge just went flying through the window. Even if that is a risk inherent in the job.
Re: “Proof” that Fuchsia will replace Linux for Google
#34I find it hard to believe that 8+ years of APIs and OS level code would be abandoned just like that, especially given the scale of Android. If this ever happens, it would probably be an extremely slow, well thought out (hopefully), well documented (also hopefully) rollout.
Re: “Proof” that Fuchsia will replace Linux for Google
#35Earlier quoted context omitted.
They've already replaced Dalvik with ART for bytecode and it was mostly transparent from what I understood. But popping up with a completely new platform API without any backwards compatibility would be very bold and risky. There would have to be a good compatibility story there. Also there is talk in the article about a POSIX layer. Now that's easier said than done. But it is Google we are talking about so they cert…
A new runtime is very different then a new framework/API/OS. The former doesn't necessarily require code changes (dalvik -> ART did not), the latter requires new everything.
Re: “Proof” that Fuchsia will replace Linux for Google
#36Again this blog? Seems we have also fake news problems here on HN. This is all fairy tale speculating for me. And I don't believe his sources. And btw: Tizen is also based on Linux. You don't build that easy a Kernel replacement.
That's not what 'fake news' means. It's perfectly clear the piece is speculative and it does not intentionally deceive (even if it turns out to be completely wrong).
Re: “Proof” that Fuchsia will replace Linux for Google
#37Doesn't putting "Proof" in quotes immediately disqualify it from being a proof?
Re: “Proof” that Fuchsia will replace Linux for Google
#38I thought google would do something like this. They didn't want to fully embrace linux so they locked all the freedom of linux away behind restrictrions in android until they had a replacement and now they are going to try to drop gnu+linux anything GPL they can... The new kernel is MIT/BSD... Welcome to Tivoization all over again. I get the need for a better kernel, the gnu+linux kernel is out of control at over 14m…
> the last thing we need is another proprietary OS on a device they built on the backs of the FOSS community If Google builds this kernel from the ground up and chooses to license it MIT, how is any binary derived from that "built on the backs of the FOSS community?"
Re: “Proof” that Fuchsia will replace Linux for Google
#39I thought google would do something like this. They didn't want to fully embrace linux so they locked all the freedom of linux away behind restrictrions in android until they had a replacement and now they are going to try to drop gnu+linux anything GPL they can... The new kernel is MIT/BSD... Welcome to Tivoization all over again. I get the need for a better kernel, the gnu+linux kernel is out of control at over 14m…
> the last thing we need is another proprietary OS on a device they built on the backs of the FOSS community If Google builds this kernel from the ground up and chooses to license it MIT, how is any binary derived from that "built on the backs of the FOSS community?"
Re: “Proof” that Fuchsia will replace Linux for Google
#40I thought google would do something like this. They didn't want to fully embrace linux so they locked all the freedom of linux away behind restrictrions in android until they had a replacement and now they are going to try to drop gnu+linux anything GPL they can... The new kernel is MIT/BSD... Welcome to Tivoization all over again. I get the need for a better kernel, the gnu+linux kernel is out of control at over 14m…
I would wager that the majority of those sloc are not compiled into the typical Android kernel, though.