41–50 of 235 posts
Another Google project that will end up being abandoned. Flutter, Dart, messaging, etc. They need to just fix Android.
Ah, the HN hivemind Markov chain is mired in another infinite cycle. https://hncynic.leod.org/
It really should be noted that this was published in 2005.
Earlier quoted context omitted.
'Animats didn't claim they were ever open. His claim was more along the lines of: Google Play Services has over time subsumed more and more of core functionality, enough to stop the creation of clones. Which is true.
Once upon a time, Android had a mail client that was part of the open source components. There was also GMail app that was closed source. Then a couple of versions later, the open source email app was discontinued and its functionality was incorporated into GMail. And the same thing has happened to many more apps and functionalities.
Another Google project that will end up being abandoned. Flutter, Dart, messaging, etc. They need to just fix Android.
Ah, the HN hivemind Markov chain is mired in another infinite cycle. https://hncynic.leod.org/
Another Google project that will end up being abandoned. Flutter, Dart, messaging, etc. They need to just fix Android.
Another Google project that will end up being abandoned. Flutter, Dart, messaging, etc. They need to just fix Android.
Also Google needs to move away from the Java ecosystem thanks to Oracle v. Google. That means dumping Android, which was built on Java entirely. Creating a new OS based on their language would seem to be in their best interests.
Another Google project that will end up being abandoned. Flutter, Dart, messaging, etc. They need to just fix Android.
> Another Google project that will end up being abandoned. Do you have any sort of evidence for this statement or is this pure speculation?
Earlier quoted context omitted.
I have a strong feeling that Fuchsia will not be abandoned. I can't put my finger on it, but Google's approach and tone around Fuchsia feels really different from how they talked about / marketed Reader, or even Wave, or other things they shut down. I'm an Android developer learning Flutter and Dart out of both curiosity and an gamble that it will likely be a faster-improving way to make cross-platform apps than othe…
...or Google+ Oh, wait
Sounds a bit like a modern, open approach to the problems that were solved by QNX. Excited to see how it evolves!
Not really open. If you submit code, you grant a license to Google to use it in non-proprietary code.[1] So, at some point, once users and developers are locked in, Google can make later versions closed and proprietary enough to stop clones. Like they did to Android with Google Play Services. [1] https://cla.developers.google.com/about/google-individual
It has always been closed source and can be replaced in any AOSP build. Google has no obligation to provide open sources apps and services on top of AOSP.
Earlier quoted context omitted.
Once upon a time, Android had a mail client that was part of the open source components. There was also GMail app that was closed source. Then a couple of versions later, the open source email app was discontinued and its functionality was incorporated into GMail. And the same thing has happened to many more apps and functionalities.
Part of that has more to do with the fact that AOSP is not used nearly as much and updating the default AOSP apps is not a good use of time for Google. The AOSP browser was never [edit: not recently] competitive with Chrome and the AOSP mail app was never [edit: not recently] competitive with Gmail.
>Fuchsia aims to provide drivers with a binary-stable interface. In the future, drivers compiled for one version of Fuchsia will continue to work in future versions of Fuchsia without needing to be modified or even recompiled. This approach means that Fuchsia devices will be able to update to newer versions of Fuchsia seamlessly while keeping their existing drivers. This is a massive step back for open source. The fa…
"Hardware vendors being unwilling to make the drivers they write open source" is a pretty fundamental reason.
Which is worse, a phone where you can't update kernel because of the closed drivers or a phone where you can update the kernel, with closed drivers? I don't think that realistically there's a third option. The open source community is not, for example, going to make their own high performance gpus.