Hacker News Reader

That's not so much a web page as a web app masquerading as a page.

Something that compiles and runs java applications in pure JS is bound to use up a shit-ton of bandwidth.

Upwards of 30MB and it took two minutes to execute the call to alert. Only for those who actively hate the visitors to their page.

> then what is this page?

A really bad example to use for bloated pages.

The website loads in 9 seconds (Chrome 50), the processing of the (peg$parseKeyword) functions takes 4.5 seconds of time during loading which causes the gap in the waterfall.

One look at the function would cause severe ingestion in most people.

(You wanted the word “indigestion”. Ingestion means something quite different. Though I suppose if someone was prone to eating when depressed, it could work.)

Its a proof of concept. Common .jars can be cached.