By the same not, more and more projects are just using gh-pages... it's useful, out there, free (of cost to those publishing) and in general works.
In the end, there's a lot of options, I think seeing IPFS support baked into the browsers will see a new wave the likes that we saw in the late 90's of customized content, and then tooling that publishes to IPFS will take hold and some things may become more standardized.
I think there is a need to get to a DNS pointer that can take one from a name to an IPFS directory (similar to a CNAME) though that may need to be updated for each publish. In the end it can/will all be very interesting to say the least.
Try out `dig +short TXT ipfs.io`, take the `/ipfs/<hash>` from that record, and go to https://ipfs.io/ipfs/<hash>. Then try https://ipfs.io/ipns/ipfs.io :)
• I don't want an article that goes viral to give me huge bills or crush a tiny server. I want automatic scaling.
• I don't want to run or upgrade a web stack. I have a few Linux VPS' and frankly they're painful to maintain. I don't have the time or energy to do this unpaid anymore. If Linux was a better OS maybe this'd be less painful.
• It's free
• They have a WYSIWYG editor that's OK (but merely OK, it's not great). Too many blog platforms want me to write in markdown or whatever.
• If I left Medium I'd lose all the followers who get notified when I write a new blog.
• There is no real value to me in doing so except maybe getting a few more features.
The main thing keeping me there right now is inertia and disinterest in self hosting.
I'm not sure that an article that goes viral can do this any more, if you're running a simple static site. Even a million hits a day on my website would only be something like 150 gigabytes of traffic a month, if it were sustained. (I'd expect a much smaller spike).
At Amazon's current pricing, that's about $15/month.