I think the important thing is to have a mitigation strategy. Google was very smart in how they commoditized cloud offerings by inventing Kubernetes. You can explode your manifests into GCP, you can explode your manifests into AWS, and it mostly works the same. Obviously you can really screw yourself by not having offsite backups (backup your GCP database into AWS, or vice-versa), or by using their proprietary stuff (Cloud Spanner, AWS Aurora). But if you're careful, you're in control, and the cloud provider is just a commodity that you pick based on price and nothing else. As an application developer, that's a great place to be.

(Similarly, I use Gmail for my e-mail, but I control the MX records. So if I get kicked off for whatever reason, I can be back up and running in no time.)

YouTube creators, however, do not have this luxury. People watch YouTube videos because they happened to be on YouTube and YouTube suggested the video, not because the end user was looking for your videos specifically. Social networks and video sharing sites are appealing to creators because there is the chance that The Algorithm (I hate that term) will award them with eyeballs that they can then sell to advertisers for very little effort. That is something you can't just migrate off of, because there are no competitors. You might convince your Patreon supporters to follow you, but even that is uncertain. I have watched many streamers move off of Twitch because they got a better deal from a competitor, only to watch their viewership drop to nothing until they were able to move back to Twitch. If one of these video sharing sites shuts you down, your career is over. Google kills your GCP account, you can still be a software engineer.

So my TL;DR is that cloud computing is very different from being an independent creator. Computers are a dime a dozen, and it doesn't matter which ones you use. But video sharing platforms give you a free audience, and that is something that is very hard to build yourself.