Hacker News Reader

A way for government employees who don't know what a command line is to edit it.

Fault tolerance in case something happens to your web server.

A way for people to read it offline when their internet connection goes down (presuming they haven't saved the HTML).

I disagree that this approach is any better than your standard static html and nginx. In an emergency situation I would want to reduce the footprint for error and keep everything as simple as possible. A CMS is totally overkill for this. There is nothing wrong with having a developer write HTML based on a word document given to them. If it were a true emergency that developer resource would be dedicated to doing this. Hell Word can export documents to HTML anyway so that is half the battle already won. This article just seems gimmicky to me.

It's adding a load of unnecessary tools and services to address a relatively simple process.

People forget how simple the web can be.

Other than service workers I don't see how this article handles points one and two. My answer there is: use a cdn.

Reply on news.ycombinator.com