this post was submitted on 04 Oct 2024
232 points (98.7% liked)

Technology

59982 readers
3902 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Badeendje 13 points 2 months ago* (last edited 2 months ago) (2 children)

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.

[–] [email protected] 9 points 2 months ago (1 children)

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".

[–] Badeendje 1 points 2 months 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.

[–] [email protected] 2 points 2 months ago

That's good advice, we will. Thank you.