It had some functionalities that nnn did not have like displaying processes or favourite directories and such. In the end I got back to nnn because I read that superfile had internet access plus the fact that I use a graphical file manager for things that nnn or many terminal file managers can not do with extensive plugins.
Uhm both displaying copy/move process and having shortcuts for “favourite” dirs is quite possible with nnn. Although for the later I mostly use -S argument for persistent session.
The only drawback of nnn in my book is the kind of weird/cumbersome way to configure it eith ENV variables. And the non-existent preview image display under wayland.
Yeah, having to customize with env variables is not great, and adding bookmarks is much easier in superfile. Anyway I suposse one does not set bookmarks to often. Plus nnn was so fast I just tapped they keys to get to the directory I needed easily. Once I learned most shortcuts I was flying trough operarions.
It wanted to download a zip file. Apparently it was a theme. But, I’m not letting a local file manager talk to the internet randomly. If I want to update it, I’ll update it myself. Or, at least provide an option to enable it on first run.
Saying Go is better than R at things R isn’t used for is a joke because it’s obvious and someone doing this in R would just draw the question of why even though they could
Did you mean 1MB? With correct settings, you get under 1MB Rust binaries and with even more compression using upx it gets to 300KB, probably less for much simpler applications. Rust applications aren’t that big of a deal as people make it to be; within reasons off course.
The one issue I have with Rust apps is how much memory they need to compile (depending on the app ofc). I could not install Pika Backup from AUR on a laptop with 4 GB of RAM for instance because the compilation would run out of memory. It’s one case where I was glad flatpak is an option.
Add comment