3 ms·

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 fo

by jlgreco 13y ago

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.

jonknee 13y ago
> 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.
- jlgreco 13y ago
  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."
  - Karunamon 13y ago
    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.
    - jlgreco 13y ago
      "Shame on the developer" does not make this any better for the consumers either.
      - Karunamon 13y ago
        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.
- jdjb 13y ago
  Woosh. He was referring to Sony and their removal of Linux on the PS3.

3 ms·

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 fo

by jlgreco 13y ago

jonknee 13y ago
> 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.
- jlgreco 13y ago
  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."
  - Karunamon 13y ago
    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.
    - jlgreco 13y ago
      "Shame on the developer" does not make this any better for the consumers either.
      - Karunamon 13y ago
        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.
- jdjb 13y ago
  Woosh. He was referring to Sony and their removal of Linux on the PS3.