4 ms·

How does this compare to https://github.com/ranger/ranger https://github.com/ranger/ranger ?

apjana 8y ago
I started writing `nnn` because of 2 reasons: - I needed something that _performs_ on the Pi which I was setting up as a _media player_ for my 3-yr old. - `ranger` wasn't an option because of slow python deps and I found ranger's changing/shifting panes very confusing. Please don't get me wrong here, I have several popular utilities in python. But when it comes to low-power, low-freq devices, the performance of interpreted or scripting languages is questionable. `nnn` also has the `du` and `navigate-as-you-type` modes which aren't readily available in `ranger` (AFAIK; I don't use it). Then you get to copy (un)quoted file path(s) even without X, `vidir` integration, terminal locker support and finally, all the painstaking optimization. The binary size is ~60KB (much lesser than the C source file that generates it). The requirements are minimal too - a c (say, musl) and a curses library. Copying file path(s) between two instances of `nnn` works seamlessly (with or without clipboard). I think the philosophy behind `ranger` and `nnn` are different and they were written to cater to different use-cases and a different audience at the very beginning. I had to write `nnn` on my desktop and at some point I noticed it works like a charm with my drop-down terminator session (I never lose any context anymore) so it became a desktop software.
agumonkey 8y ago
more minimalist, smaller, a tiny bit more responsive. Probably a lot less capable since ranger seems quite featured.
- apjana 8y ago
  In fact every operation would be slower in an interpreted or scripting language. It becomes evident on a Raspberry Pi, Linux subsystem for Windows (even on i7, yes), when opened within vim as a file chooser, or on Termux env (Android). `nnn` finds its users in all these constrained environments. Also `nnn` is not a feature by feature replacement for ranger. The last thing we want is a feature bloat. And we are very open to useful feature requests. Let us know if you are missing something.
  - agumonkey 8y ago
    We really should all develop on slow machines.
    - apjana 8y ago
      develop > test
      - agumonkey 8y ago
        that too. I did so for website. If it loads fast and render neat under elinks Ill keep it.

I started writing `nnn` because of 2 reasons: - I needed something that _performs_ on the Pi which I was setting up as a _media player_ for my 3-yr old. - `ranger` wasn't an option because of slow python deps and I found ranger's changing/shifting panes very confusing. Please don't get me wrong here, I have several popular utilities in python. But when it comes to low-power, low-freq devices, the performance of interpreted or scripting languages is questionable. `nnn` also has the `du` and `navigate-as-you-type` modes which aren't readily available in `ranger` (AFAIK; I don't use it). Then you get to copy (un)quoted file path(s) even without X, `vidir` integration, terminal locker support and finally, all the painstaking optimization. The binary size is ~60KB (much lesser than the C source file that generates it). The requirements are minimal too - a c (say, musl) and a curses library. Copying file path(s) between two instances of `nnn` works seamlessly (with or without clipboard). I think the philosophy behind `ranger` and `nnn` are different and they were written to cater to different use-cases and a different audience at the very beginning. I had to write `nnn` on my desktop and at some point I noticed it works like a charm with my drop-down terminator session (I never lose any context anymore) so it became a desktop software.

agumonkey 8y ago

more minimalist, smaller, a tiny bit more responsive. Probably a lot less capable since ranger seems quite featured.

apjana 8y ago
In fact every operation would be slower in an interpreted or scripting language. It becomes evident on a Raspberry Pi, Linux subsystem for Windows (even on i7, yes), when opened within vim as a file chooser, or on Termux env (Android). `nnn` finds its users in all these constrained environments. Also `nnn` is not a feature by feature replacement for ranger. The last thing we want is a feature bloat. And we are very open to useful feature requests. Let us know if you are missing something.
- agumonkey 8y ago
  We really should all develop on slow machines.
  - apjana 8y ago
    develop > test
    - agumonkey 8y ago
      that too. I did so for website. If it loads fast and render neat under elinks Ill keep it.