Hacker News Reader

Thanks for checking it out! By 'zero-latency', I strictly mean that there are no server round-trips to process your inputs—everything executes locally in your browser's JS engine, so there's no waiting for a backend to spin up. I hear you on the URL formatter, I'll review it to make the output actually useful. If you have any specific expectations for how it should format AMZ links, I'm all ears.

View on HN

I'd phrase that as "local" and "synchronous".

"Achieving" latency using local JS is not hard, just do some heavy compute and/or do the same via the browser's layout engine.

Try and do some real work in JS, for example, generate Sudokus, render raster images from DOM fragments, whatever: you'll see latency.

If you want non-blocking latency (like from a network request), use asnyc APIs and a Worker or other natively non-blocking API. Or simply a Promise wrapping a setTimeout.

But latency in synchronous and local JS is an everyday problem. So I think your phrasing is wrong.

Reply on news.ycombinator.com