Live data from Hacker News

Brow.sh: a modern text-based browser

brow.sh

31–40 of 113 posts

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

#31
post #25

Earlier quoted context omitted.

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

I don't think there's a single reason to use a text-based browser in a production environment.

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

#32
post #6
post #5

Earlier quoted context omitted.

Note that this isn't a "true" terminal-based browser. It's built on a WebExtension running in Firefox that renders out the DOM as text to a Go-based CLI client. It's not a browser engine running in your terminal, it's more of a VNC over TTY.

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

edbrowse has minimal js support thru duktape.

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

#33
Yes it's super slow, but many of the criticisms are missing the point. This enables browsing over SSH when you have low bandwidth. The heavy internetting is done on the remote machine (like a cloud VM for example) using blazing fast data center internet. A personal example may explain why I love this.

For several years I lived in rural Alaska where the fastest internet one could buy was $120 a month (I think) and a blazing 512 Kbps. I was a developer (working remotely) who's shop had adopted Docker, and it literally took more than 24 hours sometimes to download a docker image. By necessity I switched to having my whole development environment on a cloud VM. The Cloud VM had gigabit connection so docker downloads were blazing fast. All I needed to send across the wire was a tiny bit of text. Mosh was an absolute life saver by the way. I once flew from Anchorage to Salt Lake and had the same mosh session pick up like nothing had happened thanks to roaming abilities.

Browsing heavy (i.e. modern) websites was often very difficult too. With high latency and a lot of heavy Javascript sites requiring 10 MB or more, it was a nightmare. I occasionally went up to Eagle Alaska, where internet was even worse. The nearest cell tower was a 4 hour drive away, and the only internet was at the "library" or a crappy satellite link (that far north satellites get less useful). A tool like Browsh is a life line to people in situations like that.

In related news, when people talk about the merits of developing with just Vim vs. an IDE, I also recount the same story.

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

#34
post #31
post #25

Earlier quoted context omitted.

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

I don't think there's a single reason to use a text-based browser in a production environment.

I think you're perfectly able to understand what I meant there: anything other than research purpose in an isolated environment e.g. sandbox.

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

#35

Earlier quoted context omitted.

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?

`T` or `no-terminal=True` in the querystring will disable ANSI color codes in the response.

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

#36
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

I think my terminal's font is breaking the v2 graphs because the unfilled braille dots aren't blank rather unfilled circles. The v3 version doesn't work as my terminal doesn't support images.

On my Windows box it actually does work surprisingly well with the official curl binary and the graph looks great but the weather emoji mess up alignment towards the end.

I think these kinds of inconsistencies are the reason something like the way brow.sh does it makes more sense, if it's not plain text the only reliable way to represent it is via colored fixed width block characters as terminal UIs have been relying on those for ages so they are more widely supported.

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

#38
post #31
post #25

Earlier quoted context omitted.

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

I don't think there's a single reason to use a text-based browser in a production environment.

browsing through SSH

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

#39
post #3

It’s good to see terminal-based browsers are still being developed. I used to use w3m and lynx back in the day, and found them to be very useful at times (such as only having a GPRS signal available - makes browsing on a “full fat” browser impossible). Paired with screen (though I guess mosh would be a good option these days) to enable a resumable session in case the network dropped, of course.

I like Links more than Lynx.

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

#40

Yes it's super slow, but many of the criticisms are missing the point. This enables browsing over SSH when you have low bandwidth. The heavy internetting is done on the remote machine (like a cloud VM for example) using blazing fast data center internet. A personal example may explain why I love this. For several years I lived in rural Alaska where the fastest internet one could buy was $120 a month (I think) and a b…

But what does this do that links via ssh doesn’t already do?
Post reply on HN