• RubberDuck@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    1
    ·
    edit-2
    1 month ago

    I’d start now… these transitions usually take a bit. And Broadcom will only get more predatory. Staying with VMware is not a realistic option… especially if you rely on a support partner. With these mega corps only the other mega corps will get proper support… the rest can crawl in a hole and die

    So now is the time to figure out what replacement fits best, check your team for capability gaps and send your VMware people to courses to get intimate with the replacement.

    • CosmicTurtle0@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 month ago

      This 1000% because you know for fuck sure that some dev in the corner of a building that’s going to be the last holdout.

      Start planning now with an implementation plan to complete a few months before the contract is set to expire. Plans like these often hit bumps and delays.

      Once you’re down to the last 5%, tell them “Join or Die”.

      • RubberDuck@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        1 month ago

        Yeah… or… if your team insists on keeping VMware only for you, you will need to pay for licencing out of your own budget.