3 ms·
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
by 3np 4y ago
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)?
- tombh 4y agoI 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.
- 3np 4y agoIn case you haven't seen, here's a fun demo of what's doable in modern terminals :) https://piped.kavin.rocks/watch?v=dcjkezf1ARY https://piped.kavin.rocks/watch?v=dcjkezf1ARY (This library specifically doesn't have nodejs bindings yet, though)
- dolmen 4y agoHere is a naive implementation of (a subset of) the kitty image protocol in Go: https://github.com/dolmen-go/kittyimg https://github.com/dolmen-go/kittyimg
- mftb 4y agoWell done, this is really cool.
- GekkePrutser 4y agoOr this one which also supports sixel and iTerm protocols: https://github.com/BourgeoisBear/rasterm https://github.com/BourgeoisBear/rasterm
- octoberfranklin 4y agoDid you really just use "sixel" and "modern" in the same sentence?