NHacker Next
login
▲Show HN: Lstr – A modern, interactive tree command written in Rustgithub.com
113 points by w108bmg 7 hours ago | 36 comments
Loading comments...
berkes 1 hours ago [-]
I really love all the "modern" takes on classic tools by the Rust community.

I'm using eza (aka exa), aliased as ls, which has "tree" built in (aliased as lt), amongst others, as replacement for "ls" and it's one of my biggest production boosts in daily commandline use. Because eza has the tree built in, and the tree is also insanely fast, I won't be needing this tool - yet. Maybe one day the interactive mode will pull me over.

Congrats on releasing. And kudo's to how well you've released it: solid README, good description, good-looking gifs with exactly the right feature highlights

ipdashc 6 hours ago [-]
Seems quite cool! Though the demo gif with (what seem to be?) broken icons is a bold choice :p
w108bmg 6 hours ago [-]
lol good catch, and I totally missed it

I used vhs to record the gif which must not run the script in my native terminal! I’ll have to see about fixing it!

yonatan8070 4 hours ago [-]
I've seen a lot of people use asciinema to record and share terminal recordings, it works quite well
sdegutis 6 hours ago [-]
I didn't notice, I was too busy seeing how impressive and useful this tool is.

And with fuzzy matching built in? Just amazing. Good job OP.

drabbiticus 6 hours ago [-]
First off, the display looks great!

Second off, I didn't realize how deep the dep tree would be for this type of program -- 141 total! So much of it is the url crate, itself a dep of the git crate, but there's a bunch of others too. I'm just getting into learning Rust -- is this typical of Rust projects or perhaps typical of TUI projects in general?

(EDIT to strikeout) ~~The binary is also 53M as a result whereas /usr/sbin/tree is 80K on my machine -- not really a problem on today's storage, but very roughly 500-1000x different in size isn't nothing.~~

Maybe it's linking-related? I don't know how to check really.

(EDIT: many have pointed out that you can run `cargo build --release` with other options to get a much smaller binary. Thanks for teaching me!)

JoshTriplett 6 hours ago [-]
> The binary is also 53M

That's a debug binary, and the vast majority of that is debug symbols. A release build of this project is 4.3M, an order of magnitude smaller.

Also, compiling out the default features of the git2 crate eliminates several dependencies and reduces it further to 3.6M.

https://github.com/bgreenwell/lstr/pull/5

https://github.com/rust-lang/git2-rs/pull/1168

Stripping the binary further improves it to 2.9M, and some further optimizations get it to 2.2M without any compromise to performance. (You can get it smaller by optimizing for size, but I wouldn't recommend that unless you really do value size more than performance.)

esafak 6 hours ago [-]
No offense, but 4.3MB is huge for what it does. Most shells take less space than that! Where's all the bloat coming from?
koito17 4 hours ago [-]
> Most shells take less space than that!

Most shells dynamically link to a runtime your OS provides "for free". The 4.3 MiB binary in question is bundling the Rust runtime and its dependencies.

For reference, a statically-compiled C++ "Hello, World" is 2.2 MiB after stripping.

  % cat hello.nix
  {
    pkgs ? import <nixpkgs> { crossSystem = "aarch64-linux"; }
  }:
  
  pkgs.stdenv.mkDerivation {
    name = "hello-static";
    src = pkgs.writeText "hello.cpp" ''
      #include <iostream>
      int main() {
        std::cout << "Hello, World!" << std::endl;
        return 0;
      }
    '';
    dontUnpack = true;
    buildInputs = [ pkgs.glibc.static ];
    buildPhase = "$CXX -std=c++17 -static -o hello $src";
    installPhase = "mkdir -p $out/bin; cp hello $out/bin/";
  }
  
  % nix-build hello.nix
  ...
  
  % wc -c result/bin/hello
  2224640 result/bin/hello
esafak 4 hours ago [-]
2.2MiB for "Hello, World"? I must be getting old...

The executable takes 33KB in C, 75KB in nim.

koito17 4 hours ago [-]
By switching to e.g. musl, you can go down to a single megabyte ;)

But in all seriousness, my example is quite cherrypicked, since nobody will actually statically link glibc. And even if they did, one can make use of link-time optimization to remove lots of patches of unused code. Note that this is the same strategy one would employ to debloat their Rust binaries. (Use LTO, don't aggressively inline code, etc.)

3836293648 4 hours ago [-]
We just have large standard libraries now
wahern 3 hours ago [-]
> Most shells dynamically link to a runtime your OS provides "for free"

Rust binaries also dynamically link to and rely on this runtime.

o11c 5 hours ago [-]
For reference, some statically-linked shells on my system:

  2288K   /bin/bash-static (per manual, "too big and too slow")
  1936K   /bin/busybox-static (including tools not just the shell)
  192K    /usr/lib/klibc/bin/mksh
  2456K   zsh-static
For comparison, some dynamically-linked binaries (some old)

  804K    ./bin/bash-3.2
  888K    ./bin/bash-4.0
  908K    ./bin/bash-4.1
  956K    ./bin/bash-4.2
  1016K   ./bin/bash-4.3
  1092K   ./bin/bash-4.4
  1176K   ./bin/bash-5.0
  1208K   ./bin/bash-5.1
  1236K   /bin/bash (5.2)
  124K    /bin/dash
  1448K   /bin/ksh93 (fattest when excluding libc!)
  292K    /bin/mksh
  144K    /bin/posh
  424K    /bin/yash
  848K    /bin/zsh
(The reason I don't have static binaries handy is because they no longer run on modern systems. As long as you aren't using shitty libraries, dynamic binaries are more portable and reliable, contrary to internet "wisdom".)
JoshTriplett 5 hours ago [-]
Among the features it has: an interactive terminal GUI, threaded parallel directory walking, and git repository support. In around a thousand lines of code, total, including tests, half of which is the GUI.
oguz-ismail 4 hours ago [-]
*TUI. Not GUI
have-a-break 5 hours ago [-]
I feel like that's just the result of having a native package manager making natural bloat and a compiler which hasn't had decades of work.
CGamesPlay 6 hours ago [-]
Likely needs features tuned. I compared Eza, similarly in Rust, and it's 1.6 MiB compiled. Looking at the Cargo.toml, it includes git2 with default-features = false. https://github.com/eza-community/eza/blob/main/Cargo.toml
pveierland 6 hours ago [-]
Building in release:

  cargo build --release
  du -sh ./target/release/lstr -> 4.4M
Building with other release options brings it down to 2.3M:

  [profile.release]
  codegen-units = 1
  opt-level = "s"
  lto = true
  panic = "abort"
  strip = "symbols"
cyann 3 hours ago [-]
I did some benchmarks on one of our CLI and found that `opt-level = "z"` reduced the size from 2.68M to 2.28M, and shaved 10% on the build time, worth a try.

I'll try with `panic = "abort"` for our next release, thanks for the reminder.

fabrice_d 6 hours ago [-]
You are probably looking at a debug build. On Linux, a release build (cargo build -r) is ~4.3M, and down to ~3.5M once stripped. This could be reduced further with some tricks applied to the release build profile.
getcrunk 6 hours ago [-]
Great catch! Comments mentioned getting it down to ~2MB but that’s still humongous.

If you just think about how roughly (napkin math) 2MB can be 100k loc, that’s nuts

arlort 5 hours ago [-]
Is It though? You won't get it on an embedded device (maybe) but you could install a thousand of these tools and barely even notice the space being taken up on most machines
getcrunk 5 hours ago [-]
I think that’s a lame argument. First because it’s kind of a fallacy. Size is absolute not relative to something. Especially for software. No one thinks of software size primarily in the context of their disk space.

Further I think everyone keeps getting larger and larger memory because software keeps getting more and more bloated.

I remember when 64gb iPhone was more than enough (I don’t take pictures so just apps and data) Now my 128 is getting uncomfortable due to the os and app sizes. My next phone likely will be a 256

hnlmorg 2 hours ago [-]
I’m usually the first to complain about bloat but your counterpoints to the GPs “lame arguments” are themselves, fallacies.

> First because it’s kind of a fallacy. Size is absolute not relative to something. Especially for software. No one thinks of software size primarily in the context of their disk space.

That’s exactly how most people think about file sizes.

When your disk is full, you don’t delete the smallest files first. You delete the biggest.

> Further I think everyone keeps getting larger and larger memory because software keeps getting more and more bloated.

RAM sizes have actually stagnated over the last decade.

> I remember when 64gb iPhone was more than enough (I don’t take pictures so just apps and data) Now my 128 is getting uncomfortable due to the os and app sizes. My next phone likely will be a 256

That’s because media sizes increase, not executable sizes.

And people do want higher resolution cameras, higher definition videos, improved audio quality, etc. These are genuinely desirable features.

Couple that with improved internet bandwidth allowing for content providers to push higher bitrate media, however the need to still locally cache media.

nicoburns 1 hours ago [-]
> That’s because media sizes increase, not executable sizes.

Part of it is app sizes on mobile. But it's apps in the 200mb - 2gb range that are the problem, not ones that single-digit megabytes.

dotancohen 3 hours ago [-]
So bloated software is motivating you to spend more for the larger capacity phone?

What incentive does Apple have to help iOS devs get package sizes down, then?

vlovich123 5 hours ago [-]
When you include the code for all the dependency features this uses, you probably do end up close to 100k LoC net, no?
ethan_smith 6 hours ago [-]
Try `cargo build --release --no-default-features` to get a much smaller binary (~5-10MB) - Rust statically links dependencies but supports conditional compilation for optional features.
aystatic 6 hours ago [-]
Glancing at the Cargo.toml, the package doesn't define any features anyways. `cargo b --no-default-features` only applies to the packages you're building, not their dependencies -- that would lead to very unpredictable behavior
w108bmg 5 hours ago [-]
Really appreciate all the comments and useful feedback (first Rust package). Especially ways to reduce the size of the binary!
rewgs 1 hours ago [-]
This looks awesome! Right up my alley.

Side-note: what theme are you using in the linked gif? It's right in the middle of my two favorite themes, onedark and gruvbox.

sdegutis 5 hours ago [-]
So after writing this to learn Rust, what are your thoughts on Rust? What do you especially like and dislike about it, or what were you surprised about?
w108bmg 5 hours ago [-]
I appreciate the ecosystem of packages that seem really well maintained. I don’t love the syntax and find Rust harder to read and learn so far compared to something like golang (I’m used to R which is not a compiled language but has a great dev community).

I do love the compiler and support tools built into Cargo (fmt, clippy, etc.).

sdegutis 5 hours ago [-]
That's been similar to my experience. The ecosystem is extremely polished and smooth, the build tools and package manager and IDE support, all of it. Especially compared to C++ which I cuold barely get working here.
aystatic 6 hours ago [-]
Neat, looks like a combination of erdtree[0] and broot[1]. I use both on a daily basis, are there any features that stand out from the two?

[0]: https://github.com/solidiquis/erdtree [1]: https://github.com/Canop/broot

6 hours ago [-]
ironuchan 3 hours ago [-]
[dead]
be87581d 4 hours ago [-]
[dead]