Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ratatui – App Showcase

ratatui.rs

Post reply on HN
Print view View original

121–130 of 238 posts

Re: Ratatui – App Showcase

#121

Post by actionfromafar »

gf000 wrote: post #72
godelski wrote: post #34

I'm really waiting for the TUI web browser. That would let me live completely in the terminal. Is anyone working on this? With the speed terminals are and support for graphics through things like sixel and shaders I'd love to have a browser even if I couldn't do videos. Even if it was like viewing most pages in reader mode. I'm not sure some big companies would be happy about that though since it likely would mean yo…

But.. why? Like I do get the occasional need where it's easier to just see an html page in the terminal, but why would you render to a low-resolution 2D buffer with random character-hacks with a huge amount of overhead, over having a real buffer and just writing pixels to it, with actual hardware acceleration?

Character based interfaces are just nice, IMHO. The Borland IDE was the pinnacle of dev interfaces IMHO. It updated to have modern language server support etc would be my dream dev environment. It would be cool to see how far a compliant web browser could be taken in text mode. It's really sad that most terminals don't have proper image support, btw.

Edit: A comment here linked to https://www.brow.sh/ It looks amazing.

Re: Ratatui – App Showcase

#123

Post by nhatcher »

palata wrote: post #103
nhatcher wrote: post #76

Earlier quoted context omitted.

Hmm, that sounds bad. Were you running the debug build? Like just running 'cargo run'?

First in debug, then I built in release to see if that changed something, but it didn't. I see that there are some related discussions on the github: https://github.com/ratatui/ratatui/discussions/1927 . Not sure if there is a solution though.

Thanks! I will definitely have a look at this. I really want to like Ratatui but I do wonder how much bloat there is

Re: Ratatui – App Showcase

#124

Post by zdragnar »

diab0lic wrote: post #101

How is the Windows support in Ratatui? I recently developed something with a different library (also crossterm based) only to discover it did not work very well for my windows users and ended up having to build a GUI with Iced. There’s a very real chance I just missed some initialization code that Ratatui might do out of the box that the other library was not. Edit: Issues experienced by windows users were no colors,…

I use gitui on Windows and it is amazing, though mostly from a git bash shell.

Re: Ratatui – App Showcase

#125

Post by dspillett »

heavensteeth wrote: post #89
sunbum wrote: post #86

Earlier quoted context omitted.

Why does that link redirect to a fart sound hosted on Wikipedia?

The author doesn't like HN.

This is sort of thing is why I have a “they don't want me there, and I'm fine with that” list in my PiHole config.

Re: Ratatui – App Showcase

#126

Post by miki123211 »

weinzierl wrote: post #96
RustSupremacist wrote: post #37

People keep asking why TUIs in Rust and the answer is because the GUI situation in Rust is dreadful: https://www.boringcactus.com/2025/04/13/2025-survey-of-rust-... Rust is simply not meant for GUI-based data design but I still want Qt in Rust. That's it. Not QML or Slint. No markup at all. None of the immediate mode things. No other languages. Definitely not GTK. I'm worried it will never happen for Rust and it will…

Apart from what you said about the GUI situation in Rust (which I disagree with) I think TUI's have their niche. I think writing a useful GUI has considerable overhead no matter which technology you use. In addition they cause other difficulties, like testability, i18n, l10n and accessability. This is why people often resort to command line tools, rightfully so. There are cases, however, where a CLI won't cut it and…

To be fair, TUIs are strictly worse accessibility-wise than GUIs.

There's no standard to communicate TUI semantics to assistive technology, and whatever few standards actually exist (like using the cursor to navigate menus instead of some custom highlight) aren't followed.

With GUIs, those standards exist, and are at least somewhat implemented by all major (non-Rust)UI frameworks.

Re: Ratatui – App Showcase

#127

Post by kibwen »

RustSupremacist wrote: post #37

People keep asking why TUIs in Rust and the answer is because the GUI situation in Rust is dreadful: https://www.boringcactus.com/2025/04/13/2025-survey-of-rust-... Rust is simply not meant for GUI-based data design but I still want Qt in Rust. That's it. Not QML or Slint. No markup at all. None of the immediate mode things. No other languages. Definitely not GTK. I'm worried it will never happen for Rust and it will…

No, the people making TUIs in Rust are making TUIs because they love TUIs, and because Ratatui is pretty delightful. The state of GUI frameworks in Rust is irrelevant for this purpose, because even if there existed your ideal of Qt in Rust (putting aside the debatable notion that Qt is some sort of pinnacle of design), the people making TUIs wouldn't care, because that's not what they want to make.

Re: Ratatui – App Showcase

#128

Post by kibwen »

miki123211 wrote: post #126
weinzierl wrote: post #96

Earlier quoted context omitted.

Apart from what you said about the GUI situation in Rust (which I disagree with) I think TUI's have their niche. I think writing a useful GUI has considerable overhead no matter which technology you use. In addition they cause other difficulties, like testability, i18n, l10n and accessability. This is why people often resort to command line tools, rightfully so. There are cases, however, where a CLI won't cut it and…

To be fair, TUIs are strictly worse accessibility-wise than GUIs. There's no standard to communicate TUI semantics to assistive technology, and whatever few standards actually exist (like using the cursor to navigate menus instead of some custom highlight) aren't followed. With GUIs, those standards exist, and are at least somewhat implemented by all major (non-Rust)UI frameworks.

What you say is true, but TUIs are not strictly worse than GUIs at accessibility. The fact that text is inherently more legible than graphics means that, for example, blind players can play console-based roguelikes (and do: https://www.rockpapershotgun.com/playing-roguelikes-when-you... ), and Dungeon Crawl Stone Soup even has configuration options to improve the experience for blind people: https://github.com/crawl/crawl/blob/599108c877da33bc03cb73da...

Re: Ratatui – App Showcase

#129

Post by tomrod »

miki123211 wrote: post #126
weinzierl wrote: post #96

Earlier quoted context omitted.

Apart from what you said about the GUI situation in Rust (which I disagree with) I think TUI's have their niche. I think writing a useful GUI has considerable overhead no matter which technology you use. In addition they cause other difficulties, like testability, i18n, l10n and accessability. This is why people often resort to command line tools, rightfully so. There are cases, however, where a CLI won't cut it and…

To be fair, TUIs are strictly worse accessibility-wise than GUIs. There's no standard to communicate TUI semantics to assistive technology, and whatever few standards actually exist (like using the cursor to navigate menus instead of some custom highlight) aren't followed. With GUIs, those standards exist, and are at least somewhat implemented by all major (non-Rust)UI frameworks.

What are you talking about, a screen reader out to be way more capable in a TUI or CLI than the massive pain of ANDI or 508 compliance.

Re: Ratatui – App Showcase

#130

Post by moderation »

godelski wrote: post #51
be_erik wrote: post #40

Earlier quoted context omitted.

I use this one pretty often. It’s great. https://chawan.net/

This actually looks pretty reasonable. Thanks! I'll definitely be giving it a try

Chawan is great. Very customizable. Regular updates. Fast. The chaman utility replacing man is also good
Post reply on HN