Live data from Hacker News

Brow.sh: a modern text-based browser

brow.sh

21–30 of 113 posts

Re: Brow.sh: a modern text-based browser

#22
All I really need is showing imgs in the console, which w3m-img can do along with w3m but you need an xterm instead of the modern consoles(gnome-terminal, konsole,lxterminal, none can show imgs)

the docker images of brow.sh needs firefox and the whole pull size is a few hundred MB, can someone list the advantages over lynx/w3m/links2 etc.

Re: Brow.sh: a modern text-based browser

#23
post #18

If people are looking for an actual modern take on text based browsing, I would refer them to the work of Igor Chubin. curl https://v2.wttr.in/London curl https://cheat.sh/rsync With a supported terminal: curl https://v3.wttr.in And also: https://github.com/chubin/awesome-console-services

This is great! Does it know ahead of time if we have colors before sending the response?

Re: Brow.sh: a modern text-based browser

#25
post #6

Earlier quoted context omitted.

Ah, noted. Must check and see if w3m and lynx have evolved to cope with the modern JavaScript web!

Elinks is the only one close, but last I tried it there were still issues

Terrible suggestion.

From [1]

"On 17 March 2017, OpenBSD removed ELinks from its ports tree, citing concerns with security issues and lack of responsiveness from the developers.[5]"

Last stable is from 2009. Last development release 2012. Elinks is dead. Realize it uses an old version of Spidermonkey (JS). Elinks should not be used in a production environment, period.

[1] https://en.wikipedia.org/wiki/Elinks

Re: Brow.sh: a modern text-based browser

#26
post #18

If people are looking for an actual modern take on text based browsing, I would refer them to the work of Igor Chubin. curl https://v2.wttr.in/London curl https://cheat.sh/rsync With a supported terminal: curl https://v3.wttr.in And also: https://github.com/chubin/awesome-console-services

This is great! Does it know ahead of time if we have colors before sending the response?

No, unless it's getting info from somewhere I'm not thinking of, it has no way of knowing what terminal you're using. In principle, I think the "accept" header is the right place to put that info?

Re: Brow.sh: a modern text-based browser

#30
post #24

this is not new, (2018) please see some previous discussion https://news.ycombinator.com/item?id=17487552

This appears again and again from time to time on ycombinator.

I'm glad stuff like this does because I often forget about it, or somehow missed it before.

That said I do suspect a lot of the repeats are because there are young people on HN for whom this may be the first time since reaching an age of reason that this has hit the front page.

Post reply on HN