grpc-rust VS trendy_terminal

Rust has two: https://github.com/stepancheg/grpc-rust and https://github.com/hyperium/tonic

The typical way that I've seen is to use the build system to change out body implementations for the platform being compiled. This is modeled after the traditional notion of treating translation units like "modules" in C and C++. When I wrote Trendy Terminal, that's the route that I took. This route avoids virtual function call (dynamic dispatch) overhead.

I also did a few things: - Wrote an online e-book about Ada - Septum - context-based source code search for multi-million line codebases (I use this nearly every day at work. It's being submitted as my Ada crate of the year. - dir_iterators - library similar to the incredible walkdir. - project_indicators - library for spinners and progress bars. - trendy_terminal - library for cross-platform terminal setup, VT100 support, and GNU readline-like behavior. - trendy_test - library for simple unit testing, which runs tests in parallel. - Ada Ray Tracer - an Ada port of Ray Tracing in One Weekend. - dirs_to_graphviz - Make graphviz files from directory trees. - rst_tables - a tool to draw RST table outlines.

It does, it's not enabled by default and you can check your code page with chcp. Trendy Terminal 0.0.1 handles this for you, I should be soon releasing a 0.0.2 version of Trendy Terminal which uses an RAII type to ensure this gets reset properly for you. I'd highly recommend using "Windows Terminal" over the plain Powershell or Command Prompt.