• Scrubbles@poptalk.scrubbles.tech
    link
    fedilink
    English
    arrow-up
    24
    arrow-down
    5
    ·
    6 months ago

    If it’s not killed by google, it’s replaced with a crappier version. Having developed against many Google APIs, “deprecation” is a very frequent word they use. Most of the time there is no stated reason why an API had to be deprecated, just that it is being deprecated. They also give minimal time to switch over, the worst one I had was PubSub’s API having a mandated migration we had to perform - in under 3 weeks. Very difficult for an already tasked team of engineers who had a mountain of other more pressing work. Why I actively push against working on GCP, or google products at all. I’ve successfully pushed 2 companies away from using Google cloud now.

    Microsoft, as an example of the opposite, will have years long deprecation strategies, and usually go overboard with making sure engineers have a good replacement, and documentation on how to migrate. They have a lot to be hated for, but damn are they good with managing downstream engineers.

    • DeathsEmbrace@lemmy.ml
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      3
      ·
      6 months ago

      Wait until you realize Microsoft actually cares only because they have already analyzed and predicted that this would hurt their bottom line.

      • mindlight@lemm.ee
        link
        fedilink
        English
        arrow-up
        12
        ·
        6 months ago

        History is full of companies who went under because they didn’t analyze and predict what would hurt their bottom line…

    • FalseMyrmidon@kbin.run
      link
      fedilink
      arrow-up
      5
      ·
      6 months ago

      AWS also rarely turns off services that customers are using going so far as to support customers using outdated services for years. Of the major cloud providers only Google does this.