I'm a little skeptical of that, especially in the scenario that it's a "don't want to look at it much" situation. I've had VM's running for many, many years in an autoupgrade scenario, and it tends to just work. And the security risks are often overstated as long as you tried to minimize attack surface; so; for instance I for a while tried to track all related security issues - and at the very least 95% are irrelevant, and that last 5% is more CYA uncertainty than actual belief its relevant; I didn't find
anything positively certainly relevant.
Obviously, if your website is running a complex stack this is fairly infeasible (good luck keeping a complex web-framework secure without vigilance!) But if it's just a static site... and static sites are the fair comparison to google drive.
The issue with google drive and similar products is that they're actively - very actively - maintained. Stuff doesn't just break because it's taken offline, but because there are changes in terms of service, there are automatic deactivations for inactivity, there are plain old incompatible upgrades, etc, etc, etc.
I mean - I totally support people starting with the minimal effort (which is surely some freemium service like google drive), and leaning to live with the limitations - but the risks of a server (whether physical or otherwise) if you're similarly conservative and willing to live within constraints not unlike hosting on drive seem overblown - people talk as if servers burn down all the time, and hackers crack everything, but nothing could be further from the truth - those are exceedingly rare circumstances. And for many things, those risk are just OK. Don't keep your only copy of the data on the box, and don't keep private stuff there, and if lighting really strikes - it's not so bad. And both strategies will need a little TLC once and a while, that's just the way it is.