News for hackers. Stuff that matters.
Re:Chromecast update breaks AllCast by jlgreco on Monday August 26, 2013 @01:56PM (#6278676)
We've had a long time to prove that using automatic updates to remove features is a recipe for disaster. In fact, I seem to remember a certain company using forced updates specifically to remove users' ability to install other OSes on their devices...

Just because you can install another OS on your chromebook today doesn't mean you will be able to in the future. Get out now, or you are making a gamble.

Re:Chromecast update breaks AllCast by jonknee on Monday August 26, 2013 @02:55PM (#6279109)
> We've had a long time to prove that using automatic updates to remove features is a recipe for disaster. In fact, I seem to remember a certain company using forced updates specifically to remove users' ability to install other OSes on their devices...

They didn't remove a feature... They removed an undocumented setting for an SDK that has warnings all over the place that the API is not final and to not release an app until it is.

Re:Chromecast update breaks AllCast by jdjb on Monday August 26, 2013 @06:58PM (#6280458)
Woosh. He was referring to Sony and their removal of Linux on the PS3.
Re:Chromecast update breaks AllCast by jlgreco on Monday August 26, 2013 @04:21PM (#6279632)
From my response to somebody else in this discussion: " Hiding behind terms of use on SDKs isn't something that mellows the sting of this to users who probably don't even know what "SDK" means."
Re:Chromecast update breaks AllCast by Karunamon on Monday August 26, 2013 @07:39PM (#6280606)
Then shame on the developer for releasing an app for mass consumption based on private and non finalized APIs, and then blaming Google when things break. I understand that ragging on corporations is fun, but c'mon. Perspective , please.
Re:Chromecast update breaks AllCast by jlgreco on Monday August 26, 2013 @10:06PM (#6281039)
"Shame on the developer" does not make this any better for the consumers either.
Re:Chromecast update breaks AllCast by Karunamon on Monday August 26, 2013 @10:09PM (#6281049)
The problem the consumers are having was generated completely and totally by the developer of the app, not Google. If you as a developer write an app using non finalized APIs, and release it, and the app breaks because that API changed, it is completely and utterly your fault.