crossterm VS hub

I have this feeling with all rust apps using crossterm crate as their backend like GitUI for example

I guess you could use EventStream like in this example

Made a small toy using crossterm that simulates the falling sand using the rules laid out by day 14. Bit late to the party but was pretty fun. The moment I saw the prompt I was fully intent on making some sort of visualization for this after getting the solution.

There are plenty of terminal UI libraries that are actually nice to work with. For Python, there's Textual and PyTermGUI. For Rust, there's ratatui and Cursive (or, if you want something a bit lower level, crosster or termion). For Go, there's bubbletea.

Switching the backend of Cursive to crossterm removed dependence on ncurses

I don't know where to start, CrossTerm can read events asynchronously with tokio https://github.com/crossterm-rs/crossterm/blob/master/examples/event-stream-tokio.rs , but I don't have any idea what that really means, I am coming from the HTML Canvas and TypeScript. I want the most simple and basic method possible. Cheers!

Just wondering if anyone has any insight into the current development and maintenance of termion? It currently has 67 issues and 24 merge requests and no code activity has happened since Sep 27 2021, so nothing in over a year. I am of course grateful for the existing project, but just somewhat concerned that it ends up being abandoned or forgotten seeing as it is one of the premiere tui libraries written purely in Rust (other being crossterm).

I might make a gui frontend in the future, but for now i'll focus on the terminal. The terminal doesn't mean it doesnt support mac or windows though, they have terminals too! And the library used for accepting key-input is crossterm which supports windows!

I used crossterm. Really love the simplicity of the API, definitely fit my purposes well.

For the terminal part you could use https://crates.io/crates/crossterm

Use hub here via CLI and forget the gui https://hub.github.com/

Try automating the PR process as much as possible. Make use of tools like hub CLI for speeding up the pull request process. Code quality tools can help you automate the due diligence for coding standards and conventions, and test automation tools can assist in bug discovery, and identifying security vulnerabilities.

You can extend this: https://github.com/github/hub

parse_git_branch() { # Speed up opening up a new terminal tab by not # checking `$HOME` ...which can't be a repo anyway # # For the heck of it, micro-optimize this too: # time (repeat 1000000 { [ "$PWD" = "$HOME" ] } ) == ~4.2s # time (repeat 1000000 { [[ "$PWD" == "$HOME" ]] } ) == ~1.4s [[ "$PWD" == "$HOME" ]] && return # Fastest known way to check the current branch name # (Uses `command` to bypass wrappers like https://hub.github.com/) ref="$(command git symbolic-ref --short HEAD 2> /dev/null)" || return echo " [$ref]" }

Which will create a new remote with that name (otherwise origin will be used).

It is also less typing.

[1]: https://github.com/github/hub

I alias git to use HUB from GitHub

If you also install Hub https://github.com/github/hub it gives you a git create command, it also has a set of really useful additional CLI utilities.

SCM: Git + Hub (https://github.com/github/hub)