OTOH the highest voted comment as of this writing is comparing it to dired, so it's no worse than the competition I guess :)
OTOH the highest voted comment as of this writing is comparing it to dired, so it's no worse than the competition I guess :)
So why is the lock file so big?
1. It also locks the test dependencies, i.e. the criterion benchmarking suite which is big and it's transitive dependencies (without it's ~750 lines in the lock file).
2. The lock file is human-readable formatted, because of this every "entry" takes at least 6 lines.
3. Each entry has one additional line per dependency, but dependencies are often shared internally (e.g. libc) so this can "bloat" the lock file without adding any additional dependency.
Oh man, I do have some bad news for you if you start counting the lines in the libc or the libc++.
I would guess the 1000 lines of Cargo.lock represent ~32K of Rust code. That is probably no longer minimal by most definitions, but having a dependency on libc is like 200K of C so an additional 30K seems not so bad (assuming the dependencies are well known).
I feel you mischaracterise my GP comment though, it talked about different kinds of minimalism and said this is one valid kind.
Minimalism refers to UI/UX and not LOC.
Maybe replace minimalist with modern for a more correct description of software with 100s of dependencies? (Joke!)
Nitpicking aside, The app looks good and I do like this TUI trend!