I have been expecting WASM to take over as a common platform and eventually put browsers out of business for awhile now. I feel like browsers are bloated and monopolized.

It was invented out of pure necessity when various resources (compute, screen, network etc) were really scarce. So it is extremely information dense. No superfluous eye candy, just the Word.

In a sense the terminal is now the most respecting of our own limitations when parsing the firehose of information that is drenching every screen.

What is missing though (after all those decades) are any widely adopted conventions for how to structure anything more complex than a simple top-to-bottom text flow.

Once you move past the static page paradigm the possibilities are endless and that is not always helpful. But for a range of typical current use cases that involve information firehoses (a mailbox, an rss reader, a social media app, a wiki etc) it would be fantastic to develop common TUI design principles.

https://github.com/wtheisen/TerminusBrowser

https://github.com/bensadeh/circumflex

https://github.com/pierreyoda/hncli

https://github.com/piqoni/hn-text

https://github.com/luke8086/retronews

Disclosure: author here

I've been working on something similar [0] also running in the terminal as a TUI. It's made in Rust with a quite novel architecture described in my blog [1].

There's still a performance issue with posts having a large amount of comments but it's quite there yet.

[0] https://github.com/pierreyoda/hncli [1] https://www.newstackwhodis.com/blog/hncli-2-architecture

The author uses "libcurl" to make HTTP requests.

I prefer netcat, tcpclient and similar TCP clients, coupled with a TLS forward proxy. More flexible.

This is (very probably) the terminal app:

https://github.com/ggerganov/hnterm

gopher://hngopher.com/

But this site also renders nicely in emacs eww and is usuable in lynx(1) too.

mmm ...