History here: https://www.androidpolice.com/2018/03/02/amazon-still-isnt-s...
This is why all the pi-cast projects died down, after all. Google constantly eradicating third-party implementations to hurt Amazon.
That’s what started this fight.
If you wish to argue against this, please offer me a way to implement the Chromecast protocol on a raspberry pi, reliably, without it constantly being broken by Google’s updates.
It's core is chromecast-player https://github.com/thibauts/node-castv2-client
V2 suggests there was 1 revision over time...
The FAQ mentioned issues with Chromecast ultra and it seemed to be ipv6. Your reasoning ( Google changes a protocol to block Amazon), seems to be quite extreme.
Yes, Google does opensource a lot. But that doesn't mean they should open source one of their "few" hardware projects.
And continuing to repeatedly change the receiving protocol until everyone stopped trying to reverse it was very anticompetitive.
Amazon has spent years to get binary compatibility with almost every Google SDK and API, and Google has responded by continuing to obfuscating these even further, and preventing them entirely.
And that's in addition to Google's illegal threats (EU antitrust case is almost over) to OEMs to prevent them from building Kindle devices.
Amazon cloned an open source operating system, and used it. And attempted to achieve binary compatibility with Google's version. Google did all they could to prevent that from succeeding.
It's a very twisted view to see Amazon as having started that fight.
Personally, I dislike Google's proprietary Android versions as much as Amazon's, but it's been Google that's been fighting third party implementations all along the way here, and not Amazon. It was Google spending lots of effort to destroy open source implementations utterly and entirely.
They couldn't know that Amazon would fail miserably.. If I look at business tactics, that was a very mean move from Amazon and they earn everything that's coming ( the url's that were posted to "defend" them).
PS. I suppose you have Prime?
Trying to prevent competitors from providing compatibility with your products is anticompetitive.
In an ideal market, products are compatible, and you have multiple competitors to choose from. You could buy phones from multiple manufacturers, with different operating systems, that would be able to run the same apps. And you could stream YouTube to FireTV and Chromecast, and your FireTV could receive streams from Kindle and Google Android devices.
Amazon actively works towards providing intercompatibility whenever they can. Amazon added the same APIs to their Android version that Google closed off in Android.
Google, on the other hand, has in the past years every time they had a chance to, actively worked to prevent intercompatibility, kill standards, and limit the usefulness of open source.
I’m not sure there’s any way to see Google’s actions as a positive.
Amazon also didn't open-source anything of their changes, something Google did.
Their compatibility was a requirement for getting apps in their Amazon app store ( business decision)
Where is Google killing standards? If it is what I think you mean, they are changing the whole Android system slowly to adjust app/system updates. Balancing between open source and proprietary source is difficult and it's probably a business decision to close it more. If Amazon was successfull in taking over Android, they would have lost a lot.
https://www.recode.net/2017/10/12/16464132/google-target-ret...
https://www.pcworld.com/article/2975731/software-games/youtu...
https://www.theverge.com/2017/9/26/16371292/google-youtube-a...