As someone who hosts a lot of his own stuff, that's the real selling point of cloud hosting. Not having to care about things like spam filtering, or how some blog you want to publish is going to scale in the face of unexpected traffic.
The entire point of using cloud hosting is to pay money to not have to care about stuff like that.
I mean, why don't you let experts do what they do and you spend your time doing what you do?
Unless you do servers. In that case, sure. Whatever.
But to suggest that everyone should do (or will do it, as some people are commenting here) it is bananas.
I never said that.
The implication in your original comment is quite clear, "why don't you let experts do what they do and you spend your time doing what you do?". So, you actually did say that... But to suggest that everyone should do (or will do it, as some people are commenting here) it is bananas.
The comment you replied to didn't suggest that everyone should self host, it simply stated a preference. Your comment, however, was the exact opposite, and suggested people shouldn't self host "unless they do servers"Personally, I self host services on IaaS (Vultr). At least then I have full ownership of my data, and it guarantees I'm running on open source software that can be modified for data extraction at any time.
But the smart people are proving again and again that they are not worthy of our trust. They find bigger and better and stealthier ways to learn about us so they can influence and move against us in the future. Why should we trust anyone who sees us as a product?
I'm not sure I agree with your version of the future. People don't know enough ( and don't want to) about security, scalability, availability, etc.
I think, mainly, because life is more interesting when you do things you are not an expert of.
Yes, plus a bunch of engineers keeping the thing running.
That phrase, "just someone else's computer", has long seemed to me a piece of recklessly dismissive arrogance. Engineering cloud-based systems is simply not the same as off-cloud, and assuming otherwise will lead to dissimilar outcomes.
I can't afford a wide pipe, I can afford Digital Ocean.
If I want to spin up a server for a day or two it's much more economical to pay for a virtual server than buy one and install it in my home.
The clincher for me is email. I'm happy to configure and run a web server, maybe with a caching reverse proxy, couple of synced db servers, whatever. But configuring email just isn't worth it - I've tried. Whilst it can be setup the big players in email seem to regularly blackhole you 'just because' anyway. So the amount of time in setup and servicing just isn't worth it for a handful of domains (basically me + immediate family) unless you've got time to waste. It if a good learning experience, and I do like the control, particularly over span handling.
Even using a (small) ISP, having DKIM and SPF setup, mail sent, even as a reply, still gets spam binned often by Google, Live, be etc..
Practically it just doesn't seem to be something to do on your own.
It did take some time at the beginning to get all of the DNS stuff right, but that's a one-time cost. And, so far, I haven't noticed any spam binning once I finally got the DKIM & SPF stuff correct.
I guess part of it could be that since I'm using a lesser known ISP my IP hasn't been blacklisted as part of a large block.
If you still have an interest in self-hosting email, I highly recommend Mail-In-A-Box (https://mailinabox.email/).