3 ms·
> when when run chat programs inside electron apps, does it really matters? From a dev perspective, it's a lot easier to base64 an image you already have, with
by georgia_peach 4y ago
> when when run chat programs inside electron apps, does it really matters?
From a dev perspective, it's a lot easier to base64 an image you already have, with a base64 that's already in your stdlibs, than to scour github for a passable sixel library to pre-rasterize that jpeg & reformat it as sixel. I say this as someone who's written a sixel conversion library.
> competing formats
It's not a very old format, yet already supported on 4-5 terminals last I checked.
- retrocryptid 4y agoOr you could just use the libsixel package. Downloading libraries isn't unknown to developers (thinking about `apt-get install libncurses5-dev libsixel-dev` or the like.) Or sysadmins: `apt-get install libncurses5` or `apt-get install libsixel`.
- georgia_peach 4y ago&& find out how to get it on OSes that aren't debian-based && find a decent FFI wrapper if my app isn't in C-land && read the docs && static link hassles so I don't have to sort-out dynamic-link hassles for every platform || round-up a collection of dynamic libsixel libs & figure out how to bundle them with my script if I'm not using a compile-to-machine-code language vs b64 := base64.Encode(myImg) fmt.Printf("\x1b]1337;inline=1;size=%d:%s\n", len(b64), b64) If it's a feature request where I'm really only handling it to shut a few people up, which route am I going to take?