sl VS lc

Alas, sl is a command name already well taken. https://github.com/mtoyoda/sl

Install SL, it wont improve either, but it will make you smirk a few times per day.

My favorite "funny commands" are probably sl(1) (potentially annoying) and this ehm... "magnificent app" (potentially useful)

This kind of thing should probably be generalized so that any new parameter can be seamlessly woven into your `ls-like` reports.

https://github.com/c-blake/lc/blob/master/extensions/fe1 does `du`, but you could use `ffprobe` to do the run-time in hours:minutes:seconds for media files (or maybe 0sec for non-media) or numerous other things.

I don't know about all your other questions, but the https://github.com/c-blake/cligen CLI framework seems much lower effort / ceremony than even Rust's `argh` and is just about as old as `clap` (both started 8 years ago in 2015).

There are over 50 CLI utilities at https://github.com/c-blake/bu, many of which do something novel rather than just "re-doing ls/find/cat with a twist". While they are really more an "ls/ps construction toolkits" with some default configs to get people going, I think https://github.com/c-blake/lc and https://github.com/c-blake/procs are nicer than Rust alternatives. I mention these since you seem interested in such tools.

https://github.com/c-blake/lc can do that and more; Indeed you can group "dot directories" differently than "non-dot directories". When I sat down to write `lc` I went through all of exas issues and features and included as much as I felt reasonable.

I never liked the graphical tree mode, though. I prefer packing as much information as possible into small real estate (like cell phone terminal screens).