Unfortunately, the words "Deno", "TypeScript", and "removal" made for good headline material, and what was effectively a design document about performance optimization[1] became misinterpreted by many as heralding the removal of TypeScript from Deno, despite the document being updated with a explanatory warning that it was a very deep technical document about a specific part of architecture, and that Deno remains completely committed to supporting TypeScript forever.
Have you ever sat down and had a long, and deep conversation with someone suffering from severe paranoid schizophrenia after they've experienced a psychotic break?
I assure you, you will quickly understand the difference.
Especially if that someone is your previously un-diagnosed friend and business partner.
I think your underlying point is fair, but I'd like to see you post a more constructive explanation of where it would be useful for the analogy to capture a truth about cloud services that is not true for, say, flour - switching cloud providers is incredibly difficult due to vendor lock-in.
This is true for the source control aspects of Git, but not all of the project management aspects of GitHub. (wikis, gists, gh-pages: yes. issues, pull requests: no)