Are We Legacy Computing Yet?
8 points by pushcx
8 points by pushcx
Seems like slop? The overview tables are nigh-useless (how can ghostty support both 85% and 100% of the main set at the same time? if you look at the table sources it's apparently "100% of all 'important' glyphs", but that's never explained in the page itself), and the part about how basically no fonts support it doesn't bother to mention the usual solution to font gaps (font stacking).
It would also probably have made sense to mention the other common terminal graphics protocols (sixels? kitty graphics protocol?). "It's just Unicode and fits into the regular grid!" seems to be the main thing that SLC brings to the table, so it's weird to me that this site (probably unfairly!) consigns it to a footnote.
The selection criteria for what terminals to evaluate also doesn't make much sense to me. Ghostty and kitty, some javascript toy terminal, but no trace of the Konsole family at all?
Oh, and there's the inevitable mark of the slop, because of course there is.
Hi; I'm the author, and yes, I used Claude to write the code that generates the html tables from my (hand-authored) CSVs of the compatibility matrix. All the issues that you have with the page are proudly 100% human generated.
Normally I wouldn't respond point-by-point to a criticism of something I wrote, but since you're using it as evidence that the content is AI generated, here we go I guess:
how can ghostty support both 85% and 100% of the main set at the same time? if you look at the table sources it's apparently "100% of all 'important' glyphs", but that's never explained in the page itself
Fair point, I should probably add an explainer or at least a tooltip to show how the progress bars relate to the "important" / "not important" categories.
It would also probably have made sense to mention the other common terminal graphics protocols.
There's plenty of other websites that talk about sixel and kitty graphics, e.g. https://www.arewesixelyet.com. The reason I like SLC is that it "Just Works TM" as long as your terminal emulator supports it. You don't need to wait years for e.g. tmux, neovim, everything-else-inbetween to learn how to parse and re-output a novel graphics format.
The selection criteria for what terminals to evaluate also doesn't make much sense to me. Ghostty and kitty, some javascript toy terminal?
The "javascript toy terminal" is the one used in VS Code, estimated to be something like 75% of text editor usage worldwide.
but no trace of the Konsole family at all
Setting up terminals and doing manual inspection of their supported character sets takes an hour or two, and I don't enough about KDE to do it. But I'm not opposed to including it in the website - PRs welcome!
Let's just get it over with and have a unicode character for each possible combination of pixels on/off in a grid