Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I apologize in advance for a stupid question, but what is a "flat tree structure"? It sounds like an oxymoron.


Thanks for the question. I needed a term that would fit the README without sounding too extravagant either. Here is the explanation from fisher(7) [https://github.com/fisherman/fisherman/blob/master/man/man7/...]

Basically, a flat tree takes advantage of fish's lack of private scope (it bundles everything into the same "public" scope).

Fisherman then only needs to "load" the one single path where plugins/snippets/prompts/etc are transferred after being downloaded to the cache.

This is faster than, loading a path hierarchy per plugin and also means that performance is not affected based in the number of plugins installed.


Probably like the new npm 3 dependency directories. If A and B require a common version of C then the hierarchy is totally flat (A B C at the root). If they require incompatible versions of C then there will be 2 C, one nested inside A and one inside B


npm 4 dep management is more complex. In fish there is no private function scope so things are much simpler (but not as powerful indeed).




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: