tonic VS tui-rs

Use tonic-build directly from Rust.

} // Omit the remaining code and refer to the example in Tonic: https://github.com/hyperium/tonic/blob/master/examples/src/multiplex/server.rs ```

If I’m not misunderstanding, you could both decode the gRPC protobuf AND write to delta lake in Rust. Tonic, Delta-rs.

Original post: https://github.com/hyperium/tonic/issues/1405. Cross-post here in case the problem is not specific to tonic.

Tonic

Just to double check Is this the correct repo?

Wasm isn't involved much actually. Basically, the frontend asks the backend to perform a gRPC call on its behalf using Tauri events. They are like named channels on which you can send any serde-compatible value. But the backend is a normal Rust program so there are no constraints there. I use prost-reflect to encode/decode Protobuf messages according to Protobuf descriptors loaded at runtime and make the actual requests using tonic from the tokio ecosystem. prost-reflect is necessary because, normally, tonic expects the Protobuf descriptor to be known at compile time so it can make some code generation behind the scenes.

You could have a look at gRPC i.e. https://github.com/hyperium/tonic

Looking at this example code: https://github.com/hyperium/tonic/blob/master/examples/src/tower/server.rs

The remaining gap is remote actors, since you still need some kind of serialization between them, and take your pick of standards for that one such as gRPC using Tonic.

The TUI is built with the awesome Ratatui [0] library (formerly tui-rs [1]). UX is certainly not my area of expertise and I would not have been able to create Trippy without this library.

[0] https://github.com/ratatui-org/ratatui

[1] https://github.com/fdehau/tui-rs

Rust has great libraries for TUIs. tui-rs (https://github.com/fdehau/tui-rs) has been used in numerous popular applications, but is unmaintained. ratatui (https://github.com/tui-rs-revival/ratatui) is the maintained version, and is pretty new. Less widely known is cursive (https://github.com/gyscos/cursive), which I have yet to try.

Aside from the libraries, I just wanted to start a project that would make be better at Rust. The easy distribution with cargo is a huge bonus though.

CLI, use Clap. If you want to get fancy, use Tui.

u/lordnacho666 It uses the fabulous https://github.com/fdehau/tui-rs (now revived as https://github.com/tui-rs-revival/ratatui) TUI lib.

This app is based on the these two crate in rust (tui-rs , tui-textarea). The text area provide the Emacs motions and I integrated the vim motions there, but the editor in this app as much simpler than the huge VIM and Emacs systems

If you interested in the TUI apps in rust you can start with the crate tui-rs or its revival ratatui. They have examples inside of them which you can start and see the source code to get the basic functionalities. For the text editor you can check examples in the crate tui-textarea.

For Golang there is Bubbletea [1], Textual [2] for Python and tui-rs for Rust [3].

[1] https://github.com/charmbracelet/bubbletea

[2] https://github.com/textualize/textual

[3] https://github.com/fdehau/tui-rs

You can check tui-rs, is a library to build CLI interfaces and has some examples about using user input without blocking the UI