Browsh – A fully-modern text-based browser, rendering to TTY and browsers

Re:Browsh – A fully-modern text-based browser, rendering to ... by 3np on Tuesday May 24, 2022 @07:20AM (#31490585)

For the terminal use-case, what would your stance be on exploiting modern terminal functionality for e.g. high-res images (cf. kitty protocol, notcurses, sixels)?

[ Parent | on HN ]

Re:Browsh – A fully-modern text-based browser, rendering to ... by tombh on Tuesday May 24, 2022 @07:42AM (#31490758)

I was for a long time against that, simply because it can't be represented as text. But now I understand that sixels are just more text-based ANSI escape codes! So I'm on board again, but I'm not so personally interested in it, so it's not a priority at the moment.

[ Parent | on HN ]

Re:Browsh – A fully-modern text-based browser, rendering to ... by 3np on Tuesday May 24, 2022 @07:50AM (#31490815)

In case you haven't seen, here's a fun demo of what's doable in modern terminals :)

https://piped.kavin.rocks/watch?v=dcjkezf1ARY

(This library specifically doesn't have nodejs bindings yet, though)

[ Parent | on HN ]

Re:Browsh – A fully-modern text-based browser, rendering to ... by dolmen on Tuesday May 24, 2022 @07:52AM (#31490832)

Here is a naive implementation of (a subset of) the kitty image protocol in Go: https://github.com/dolmen-go/kittyimg

[ Parent | on HN ]

Re:Browsh – A fully-modern text-based browser, rendering to ... by GekkePrutser on Tuesday May 24, 2022 @11:18AM (#31493235)

Or this one which also supports sixel and iTerm protocols:

https://github.com/BourgeoisBear/rasterm

[ Parent | on HN ]

Re:Browsh – A fully-modern text-based browser, rendering to ... by mftb on Tuesday May 24, 2022 @09:13AM (#31491599)

Well done, this is really cool.

[ Parent | on HN ]

Re:Browsh – A fully-modern text-based browser, rendering to ... by octoberfranklin on Tuesday May 24, 2022 @08:18AM (#31491031)

Did you really just use "sixel" and "modern" in the same sentence?

[ Parent | on HN ]