Rust TUI Framework Comparison

This page is not a ranking. It is here to help you decide:

Short version

If you mainly want a stable widget toolkit, Ratatui is still the most established starting point.
If you want a more traditional view/callback style terminal app, Cursive is straightforward.
If you want a component-oriented terminal UI with explicit event flow, Tuirealm is worth a look.
If you want a broader declarative UI mental model across platforms, Dioxus TUI may feel more natural.
If your main problems are long-running sessions, streaming output, viewport/history semantics, and localized updates, Ansiq is positioned differently.

Framework	Core model	State model	Update path	Best fit
Ansiq	runtime-first retained tree	signal / computed / effect + app messages	dirty scope -> subtree replacement -> partial relayout -> patch	agent shells, monitors, explorers, long-running terminal workspaces
Ratatui	immediate-mode widget toolkit	app-managed state	render each frame into a buffer	dashboards, tools, mature widget composition
Cursive	view tree + callbacks	callback-driven local app state	event loop updates views	forms, menus, traditional TUIs
Tuirealm	components + events/messages	component state + orchestration	event-driven component updates	componentized terminal apps
Dioxus TUI	declarative component tree	hooks / signals style state	renderer-driven updates	teams that want a shared mental model across web, desktop, and TUI

Ansiq is not primarily trying to be “another widget set”. Its center of gravity is:

That is why Ansiq feels more like a terminal runtime than a plain widget library.

If your main need is:

a broad and battle-tested widget set right now
no long-running shell or transcript semantics
getting a business UI on screen quickly without caring much about runtime boundaries

then a stronger starting point is often:

Ansiq is more compelling when your app has to coordinate all of these:

That is the niche where its runtime-first design matters most.