Live data from Hacker News

Show HN: Browsh – A modern, text-based browser

brow.sh

11–20 of 330 posts

Re: Show HN: Browsh – A modern, text-based browser

#15
Pretty sweet!

Curious: why headless firefox and not headless chrome? Also: 'its main purpose is...to reduce bandwidth.' How does this reduce bandwidth? Is the assumption that you would deploy browsh on a server and ssh/mosh against that, and the bandwidth savings are to the client? (But full bandwidth usage to the server)?

Re: Show HN: Browsh – A modern, text-based browser

#16
post #14

> Its main purpose is to significantly reduce bandwidth and thus both increase browsing speeds and decrease bandwidth costs. How does it reduce bandwidth exactly? It still has to grab all the html/css/js for the site being rendered.

does it fetch images? if it does not, there you go..

Re: Show HN: Browsh – A modern, text-based browser

#18
post #14

> Its main purpose is to significantly reduce bandwidth and thus both increase browsing speeds and decrease bandwidth costs. How does it reduce bandwidth exactly? It still has to grab all the html/css/js for the site being rendered.

I think the use-case is that the user is running their headless browser on a remote server with a good internet connection. Then they open an SSH tunnel to that server from their local machine which has low bandwidth--and the only thing that needs to be received by the local machine is the browsh rendering of the webpage.

Re: Show HN: Browsh – A modern, text-based browser

#19
post #15

Pretty sweet! Curious: why headless firefox and not headless chrome? Also: 'its main purpose is...to reduce bandwidth.' How does this reduce bandwidth? Is the assumption that you would deploy browsh on a server and ssh/mosh against that, and the bandwidth savings are to the client? (But full bandwidth usage to the server)?

Because Firefox is open source, in the same vein as this project? Just a guess.

Re: Show HN: Browsh – A modern, text-based browser

#20

> Browsh consists of a minimal Golang CLI client and a browser webextension. Most of the work is done by the webextension. When the CLI starts, it looks for a compatible browser (currently only Firefox) and starts it in headless mode. Once the browser has started it opens a remote debugging connection and installs the extension. So a browser wrapper .

Why wouldn’t you just use lynx?
Post reply on HN