3 ms·
Funny thing, as popular as sixels are now, they were pretty useless back in the day. It would take ages for a picture to appear on a VT terminal with those slow
by wkat4242 4y ago
Funny thing, as popular as sixels are now, they were pretty useless back in the day. It would take ages for a picture to appear on a VT terminal with those slow serial speeds (VT320 doing 19200 baud max! - not sure about the 330/340). Especially with colour. I'm pretty sure the later ones (I have a VT520 myself) didn't even have it anymore!
I know word perfect for Unix used it for the print preview but I don't know any other app from those days that used them at all. The same with the double width or height fonts the VT series offers. I've only ever seen them working when running vttest. They could be very useful, but in practice I've never seen them actually used for something other than testing.
These days with pretty much unlimited speed sixels actually become useful. But they don't support full 24 bit colour so another technique is probably better for today's needs. For example it would be great to be able to define a terminal region and send images and video to it with full hardware acceleration and compression (H.264 or similar). I think there's still a good usecase for terminals, but holding on to sixel feels a bit too much of a kludge to me. If they were super abundant and popular, sure. But they never actually were.
I think this is also why kitty chose to build a custom protocol instead of implementing sixel.
- JdeBP 4y agoI wonder about the popularity. There are a number of examples in the long Microsoft Terminal issue discussion about sixels, but very little of it seems to be day-to-day tasks. Whereas people are getting inventive with Unicode in the little ways, from clever progress bars and spinners to tiny but importantly everyday things like arrows in shell prompts. I just myself wrote a pseudo-window login dialogue (a replacement for the login(1) program for framebuffer terminal emulators that can do Unicode) using MouseText from the Apple IIc, which got added to Unicode version 13 in 2020. * https://tty0.social/@JdeBP/110373938216006335 https://tty0.social/@JdeBP/110373938216006335
- wkat4242 4y agoYes the spinners that are made of braille are nice. And graphs. But unicode support is pretty ubiquitous now. It works great. Despite advanced unicode (ligatures, emoji) not really playing nice with monospaced fonts, most terminals handle it very well.
- wkat4242 4y agoBy the way yes it's relatively popular, out of the various options. Sixels are more popular than Kitty's protocol and what iTerm2 has. Though more and more console libraries are supporting multiples of these which will help get more reach for all of them.
- kragen 4y agoi did see people use the double-width and double-height fonts custom splash screens for logins and app startup and stuff they were novel but they weren't actually good. that goes double for sixel: it was pretty cool to see the system manager loading a color image on his vt340+ but we're talking about a postage stamp per second. you could see the individual color planes loading the vt340 was a misguided engineering dead end. i think even the vt100 was a mistake, given that they had to put an entire computer inside of it to make it work, and it would have been a lot nicer to rethink how terminals could work in light of the new possibilities opened up by vlsi which, of course, is how we got not just supdup but the apple ][, the commodore 64, the hp-41c, the macintosh, lantastic, netware, doom, etc.
- wkat4242 4y ago> they were novel but they weren't actually good. that goes double for sixel: it was pretty cool to see the system manager loading a color image on his vt340+ but we're talking about a postage stamp per second. you could see the individual color planes loading Yeah that was my point. It was so slow it was really only usable for the usecases bringing extreme value. A vector drawing protocol like tectronix (still included in xterm also) would have been preferable. > the vt340 was a misguided engineering dead end. i think even the vt100 was a mistake, given that they had to put an entire computer inside of it to make it work, and it would have been a lot nicer to rethink how terminals could work in light of the new possibilities opened up by vlsi The VT340 yes. I don't think the VT100 was a dead-end. It wasn't the most popular terminal of its day for nothing. This was the time when microprocessors started powering everything from microwaves to fridges. A "whole computer" was still simpler than the VT05 which had no "computer" but a whole stack of PCBs full of discrete electronics. See how horribly deep it was to house all those electronics: http://terminals-wiki.org/wiki/index.php/File:DEC_VT05_121708587772-2.jpg http://terminals-wiki.org/wiki/index.php/File:DEC_VT05_12170... . And despite all that its terminal protocol was super basic, it wasn't a lot more than a screen-based teletype. I think it's one of the most beautiful designs of the day though. Very star trek. The VT100 was a computer yes (there was actually a standalone CP/M version of it called the VT180). But it didn't really compete with PCs, it was a logical choice if you had a centralised minicomputer which was still very common back then. Being 'cheap' was relative only to the central computer which was a huge investment. And of course its successors were way cheaper and smaller (the VT220 and VT320 in particular). I think the 320 was a really nice form factor, the 220 still had fairly chunky bezels. I still own a VT520 myself but it has a distinct "generic VGA monitor" feel. It is the most capable of the range for using it in this day and age though (which doesn't mean a lot, a lot of *nix software these days just blasts xterm without bothering to check termcap or terminfo).