426 points by vinhnx 6 days ago | 223 comments | View on ycombinator
joouha 6 days ago |
tptacek 6 days ago |
kodoman 6 days ago |
I don't generally like TUI's and think one gets more flexibility with raw text interfaces and being able to glue things together is more important then them looking nice. I think less fancy out put is better to be honest.
user-error 6 days ago |
1. The AI disclosure up front is very useful for cutting my blog filter time from 10 seconds down to 1, which is significant in the age of content overload. Hopefully disclosure becomes a point of pride for vibebloggers and they'll add it more often.
2. While it makes sense that the popularity of TUIs (driven mostly by CLI coding agents) sees maintainers try and push more spec into emulators, I'm hoping this doesn't become the standard. The whole TUI mentality just runs counter to what makes terminals such sticky tech in the first place.
matheusmoreira 6 days ago |
nottorp 6 days ago |
What's the reality with these new frameworks? Whenever I see one i worry that it renders at 144 Hz in a loop instead of redrawing only when something changes, for one. And let's not mention redrawing only the areas that have changed [1].
Should I ask about ram consumption too?
[1] ... which is why vi is the best editor to use over slow, unreliable links.
montroser 6 days ago |
captainmuon 6 days ago |
nixpulvis 6 days ago |
cobychapple 6 days ago |
hnlmorg 6 days ago |
But for there to be a dedicated section on how multiplexors wouldn’t work suggests to me that the authors already tried this via tmux.
So I’m left wondering what they’ve done with the implementation of this to make that a problem.
I spotted they are using DCS sequences. But even that shouldn’t be an issue itself.
joshka 6 days ago |
There's some bits that feel like they probably make sense to consider doing other ways, like how border placement works (inside, outside, on the border, etc.), and how the filling works - to make borders incorporate external or internal padding.
CGamesPlay 6 days ago |
errnoh 6 days ago |
Interestingly enough the kitty author has declined a feature request similar to this couple years ago in https://github.com/kovidgoyal/kitty/issues/7511 but the approach here seem to have not resulted in any of the major pains he was expecting in that message. It is valid point that implementing something like this on a single terminal might not be worth it, but now we have poc available for two major ones I guess?
Anyways, branch and write-up available here: https://github.com/errnoh/kitty/blob/cell-borders/CELL-BORDE...
(The usual disclaimers apply: all of the actual code is AI written)
yonatan8070 6 days ago |
Somthing I think could be intresting to go along with this is for the terminal to be able to distinguish sub-windows using these border, so if you've got a popup and try to select multiple lines in it, you'll actually select only the text in thr popup rather than the whole terminal-wide line.
weinzierl 6 days ago |
A while ago I coded this up with a Ratatui subset on the Commodore[2] but I think this paradigm could be useful for modern TUI apps as well. One example I'd use that for is a minimap, which is quite awkward to do in characters.
[1] Plus the occasional whole screen offset and raster effects.
[2] Code is not public yet but there is a screenshot how it looks. https://github.com/weinzierl/8-bit-rust
inguz 5 days ago |
But... "nicer than box-drawing characters" is such a low bar. The semigraphics are right there, and can be beautiful! They've been part of DOS (cp437) since the very beginning, and Unicode has a more-than-adequate variety.
Here's my afternoon's experiment: `prtty`
nkmnz 6 days ago |
ianberdin 6 days ago |
andix 6 days ago |
Instead of adding extension over extension on top of some old protocol. And using a lot of hacks to get stuff done.
pkulak 6 days ago |
The charm of the terminal is that you can do whatever you want, as long as it fits in one cell.
nmstoker 6 days ago |
Evidlo 6 days ago |
Is it because it looks visually crowded?
octoberfranklin 6 days ago |
dead_hn_theory 6 days ago |
TacticalCoder 6 days ago |
So the "borderless" (0 pixels) / zero "useless gaps" simply are confusing and... Wrong.
But then people who do use useless gap, as in TFA, get it wrong too: they typically add gaps near the monitor's edges.
Yeah. But no. Sorry but my monitor's edge is a perfectly fine gap. I don't risk mistaking it for anything.
So I modified my WM (the Awesome WM) to do proper "useless gaps" computation and remove the ones that really are useless: and that'd be those near the monitor's physical border.
I mean: nearly everybody gets it wrong, but it's not complicated to get it right, is it?
P.S: even the terminology is wrong... People calling those "useless gaps" haven't got a clue: they are useful. The only useless ones are the one on the monitor's edge (if your monitor has physical edges, which it probably does).
0c3ca83 6 days ago |
tripa 6 days ago |
krautburglar 6 days ago |
wg0 6 days ago |
jiehong 6 days ago |
It reminds me of video games overlays / layers (like the gameboy window layer) used to display HUDs.
db48x 6 days ago |
godDLL 4 days ago |
xixixao 6 days ago |
mfld 6 days ago |
charles_f 6 days ago |
I probably missed on something, but I stopped there
codesnik 6 days ago |
[background color, top, left, bottom]B[top, bottom only]UTTO[top, bottom, right]N[reset]
ganelonhb 6 days ago |
eviks 6 days ago |
vessenes 6 days ago |
merelysounds 6 days ago |
I like simple, predictable TUIs which i can operate with keyboard input only. I don’t like ui chrome or complex ux in TUI, i prefer GUI for that.
lilbigdoot 6 days ago |
kevin_thibedeau 6 days ago |
movingimage 6 days ago |
movingimage 6 days ago |
favori995749721 6 days ago |
The part I'd want specced early: borders are per-cell, but cells aren't per-grapheme. A CJK char owns two cells plus a continuation placeholder, and combining marks or ZWJ emoji sequences own zero-or-more depending on whose wcwidth table you ask, so app and terminal routinely disagree across Unicode versions. Today that shows up as a vertical bar one column off; with cell borders it becomes a line that stops short of the corner. Does the border attach to the cell or to the grapheme cluster?
yoy0721 6 days ago |
dharmasthan 6 days ago |
kenzo_cavanaugh 6 days ago |
undefined 6 days ago |
milosz0010 6 days ago |
Unfortunately mintty is the only terminal emulator I'm aware of which supports overstrike [0], as this would open up a world of new possibilities for TUI apps if more widely supported.
[0] https://github.com/mintty/mintty/wiki/CtrlSeqs#overstrike