Hacker News Reader

Seems an odd choice for a developer, for sure. I'm with all those who also have pointed out that self-hosting is the better route. Heck, as mentioned here, a compromise for this particular user would be to host the code on github and then use github pages for a nice companion site.

View on HN

I typically go the github pages route. I used to buy domains for every project I spun up, but the collective bill started to add up for a bunch of very low traffic sites for projects that didn’t pan out. Now I just use github.io.

The other concern is legacy. I’m getting up there in age. I would like some of my work to continue to be useful after I retire without me paying for domain renewals or worrying about hosting. Without my intervention a github.io site will probably outlast a onionisafruit.com site.

> but the collective bill started to add up for a bunch of very low traffic sites for projects that didn’t pan out.

Then maybe group them on a domain with subdomains or just subpages?

Reply on news.ycombinator.com