lazy-table VS django-tables2

Good question! lt.stream has an artist argument which is responsible for how to render the table (there are more details on how to use this in the README). The default choice of artist will not mangle your terminal output so you can "scroll up" naturally. However, there are artists that will mangle your terminal output. An example is artist=lt.artists.Console(clear=True), which clears the TTY whenever a new row is generated.

If you are interested, pip install lazy_table and check out the example in the README on the GitHub page: https://github.com/parsiad/lazy-table. PRs are welcome!

How does this compare to https://github.com/jieter/django-tables2? That one makes it really easy to display database models with column sorting and pagination.

The degree of reusability (Thanks to things like GenericForeignKey and the ubiquity of Django Templates and Django ORM, there are tons of reusable components like django-filter or django-tables)

In Django there is django-tables2 for example, that creates html table from database query.

(eg. "Django apps" like django-filter and django-tables2, which rely on being a slice across the ORM, controller layer, and templating engine.)

From the readthedocs tutorial, A few examples:

I don't see how Axum would enable something like django-tables2 or django-filter which has is vertically integrated with Django's ORM, routing layer, and template system.

I've used actix-web for stuff... but I'm just sick of constantly reinventing the rote boilerplate that things like django-tables2 and django-filter generate for me once I've declared whatever customizations I want.

django-tables2 - like crispy forms but for tables, abstracts away the need to render tables in a template.