[0]: https://news.ycombinator.com/item?id=4017933

[1]: https://kerrick.github.io/google/

And my wife, wonderful as always, helped critique the writing! My RadioMenu class's comments (in the "See More: Inline menu example" expando-section) were far worse before she helped.

https://github.com/marcoroth/bubbletea-ruby

- You don't have control over font size and your color palette can be limited (and chosen by the user in their Terminal settings), so it's hard to go too off-the-rails in aesthetic design

- You work on a strict character grid, so it's hard to get things like padding, margin, and leading wrong.

- You can't assume the use of a mouse, so everything has to work on keyboard shortcuts. This usually leads to extremely power-user-friendly tools. Plus, keyboard-driven, power-user-friendly UIs are hot right now, even on the web (Linear, Fernand, etc.).

[0]: https://git.sr.ht/~kerrick/ratatui_ruby/tree/783a08eabe2307f...

[1]: https://www.ratatui-ruby.dev/docs/v1.0/examples/app_color_pi...

I've carefully stewarded & heavily edited the Ruby code in lib/ and test/, and the documentation (RDoc and Markdown). The Rust code has been left largely to the AI, with its quality kept presumably-okay by Clippy and extensive automated tests on the Ruby side.

As for the non-library stuff ("internal" to the project), you can tell by browsing the tasks/ folder where I left the AI to its own devices [1], and where I heavily edited the Ruby code [2].

[0]: https://man.sr.ht/~kerrick/ratatui_ruby/history/ecosystem-dr...

[1]: https://git.sr.ht/~kerrick/ratatui_ruby/tree/783a08eabe2307f...

[2]: https://git.sr.ht/~kerrick/ratatui_ruby/tree/783a08eabe2307f...