broot
jpeg-decoder
Our great sponsors
broot | jpeg-decoder | |
---|---|---|
41 | 4 | |
10,068 | 146 | |
- | 1.4% | |
9.1 | 6.0 | |
9 days ago | 3 months ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
broot
-
Use Midnight Commander like a pro (2015)
Take a look at broot https://github.com/Canop/broot
-
Johnny Decimal: A System to Organize Projects
A past coworker implemented a system like this. It was awful. He was the gatekeeper because the numbers and names had to be "just so" to meet his approval, and he was the most senior person on the team. He was neurotic in general and a pain to work with.
The idea of limiting yourself to a few top-level categories in a directory hierarchy and then doing the same with subdirectories makes sense, but adding numbers is a bad idea. It just creates more work, and other people have to learn your idiosyncratic nomenclature. Just give the directories good names and get on with it. Search really isn't as bad as the article suggests, especially with something like broot [1].
[1]: https://github.com/Canop/broot
- Broot: A new way to look at file management written in Rust
-
Antonmedv/walk: Terminal file manager
I've used a lot of the tools mentioned here in comments, but I think just for finding a directory/file broot[1] is much faster and easier than others. Though it is also quite feature rich but mostly it's just write a fuzzy search term that could even be sub-sub-directory and open, extremely quickly.
[1] https://github.com/Canop/broot
-
Projectable: A TUI file manager built for projects
`broot` (https://github.com/Canop/broot) is another file manager with a curious interface that seems to fill a similar niche.
Of course, there are many other file managers to choose from (mc, ranger, nnn, lf, ....), but most of them don't show nested subdirectories by default.
-
Report on platform-compliance for cargo directories
As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.
-
erdtree v1.2.0, a modern multi-threaded alternative to `du` and `tree` now with support for globbing, icons, and more
You may be interested in broot
-
bsdutils: Alternative to GNU coreutils using software from FreeBSD
I think you’re conflating different projects.
There are projects that aim for a better user experience, with better command line interface, defaults, performance and UI. These are of course breaking changes and the programs can’t be used as drop in replacement. Some examples are
- ls => exa (https://github.com/ogham/exa)
- grep => ripgrep (https://github.com/BurntSushi/ripgrep)
- cat => bat (https://github.com/sharkdp/bat)
- tree => broot (https://github.com/Canop/broot)
The person you’re replying to was speaking of a different project - uutils (https://github.com/uutils/coreutils). These are drop in replacements with identical interfaces (modulo bugs).
-
Reading Ebooks on the Commandline
Even better broot, previously adding view verb to config:
-
Is possible to configure "micro" terminal text editor with "broot" tool, to open text file with micro?
Broot: https://github.com/Canop/broot
jpeg-decoder
-
[Media] I stumbled upon this when reading an ARM vs x86 comparison, and it made me giggle
… but that's a problem surprisingly limited to C or 'find symbols by name'-land. Inside a Rust executable, there is no problem applying multiversion or manual alternatives to relevant methods that are actually in the hotpath, and thus executing them with a recent instruction set while being compatible at the same time. That's infinitely harder if you can't simply compile the function multiple times because it would lead to (undetected, dynamic) linker conflicts en-masse.
-
Which open-source Rust projects have getting-started bugs/FRs?
Given your qualifications, optimizing the Huffman decoding in jpeg-decoder crate sounds like a good opportunity. 50% of the entire decoding time is spent there; any improvements in it would translate to significant performance gains for decoding JPEG images. The tracking issue is here: https://github.com/image-rs/jpeg-decoder/issues/155
-
The last and next year of image-rs
Thanks. Issue filed [here under jpeg-decoder module](https://github.com/image-rs/jpeg-decoder/issues/185)
What are some alternatives?
fzf - :cherry_blossom: A command-line fuzzy finder
rav1e - The fastest and safest AV1 encoder.
nnn - n³ The unorthodox terminal file manager
image - Encoding and decoding images in Rust
xplr - A hackable, minimal, fast TUI file explorer
abstreet - Transportation planning and traffic simulation software for creating cities friendlier to walking, biking, and public transit
zoxide - A smarter cd command. Supports all major shells.
image-core - Core set of types and traits for image encoding and decoding
lf - Terminal file manager
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
voidrice - My dotfiles (deployed by LARBS)