Live data from Hacker News

Exa Is Deprecated

github.com

41–50 of 244 posts

Re: Exa Is Deprecated

#41
post #26
post #11

Earlier quoted context omitted.

I wish there was a better way for the community to handle this situation without the original author doing what we see here. Sometimes the original author dies unexpectedly for example and it's very hard to salvage the work into a maintained fork. I wrote about this in 2018: https://kodare.net/2018/06/25/salvaging-abandoned-projects.h...

There is, I created it years ago, but unfortunately it hasn't taken off: https://www.codeshelter.co/ Maybe I'm bad at marketing, it seems like a pity.

Man, that's amazing! I'm going to start help you with marketing, beginning with a dedicated HN post: https://news.ycombinator.com/item?id=37417410

Re: Exa Is Deprecated

#42
post #26
post #11

Earlier quoted context omitted.

I wish there was a better way for the community to handle this situation without the original author doing what we see here. Sometimes the original author dies unexpectedly for example and it's very hard to salvage the work into a maintained fork. I wrote about this in 2018: https://kodare.net/2018/06/25/salvaging-abandoned-projects.h...

There is, I created it years ago, but unfortunately it hasn't taken off: https://www.codeshelter.co/ Maybe I'm bad at marketing, it seems like a pity.

The idea is good. There's a couple of things I'd like to see. Is CodeShelter community-owned and driven? Or is it a company? The website codebase has no license and the Github application code is not open-source (or I overlooked). There's no privacy policy, ToS, and CoC. What is the maintainer vetting process? How is matchmaking taking place? What can I expect after giving away control? This may all be well-organized, but you can only find out in chat. So asking "Give us access to the repository" is a big step.

Re: Exa Is Deprecated

#43
post #11
post #2

I hope that the author Benjamin Sago is alright. It's always concerning when FOSS developers disappear for a while - even though it isn't uncommon.

I wish there was a better way for the community to handle this situation without the original author doing what we see here. Sometimes the original author dies unexpectedly for example and it's very hard to salvage the work into a maintained fork. I wrote about this in 2018: https://kodare.net/2018/06/25/salvaging-abandoned-projects.h...

> it's very hard to salvage the work into a maintained fork.

How is it hard? Just fork it.

Re: Exa Is Deprecated

#44
post #4

I've been using LSD instead of Exa, so I'm lightly relieved that I don't have to change over. Both projects are amazing little utilities that when combined with a well-customized shell, really make using the terminal a joy. I absolutely love the trend of rewriting classic Unix utilities in rust, because the new tools often have (small or large) usability and quality of life improvements that altogether make the termi…

> I absolutely love the trend of rewriting classic Unix utilities I avoid them unless I'm capable of maintaining them myself. My primary reason for using classic Unix utilities is trusting that they'll still work in a few years. The initial stages of a rewrite can be a lot of fun, but I want to use it long after the excitement has worn off.

YMMV, but many of us find it easier to maintain rust + cargo than the old C + autotools mess.

Re: Exa Is Deprecated

#45
post #41
post #26

Earlier quoted context omitted.

There is, I created it years ago, but unfortunately it hasn't taken off: https://www.codeshelter.co/ Maybe I'm bad at marketing, it seems like a pity.

Man, that's amazing! I'm going to start help you with marketing, beginning with a dedicated HN post: https://news.ycombinator.com/item?id=37417410

Thank you!

Re: Exa Is Deprecated

#46

Earlier quoted context omitted.

> I absolutely love the trend of rewriting classic Unix utilities I avoid them unless I'm capable of maintaining them myself. My primary reason for using classic Unix utilities is trusting that they'll still work in a few years. The initial stages of a rewrite can be a lot of fun, but I want to use it long after the excitement has worn off.

YMMV, but many of us find it easier to maintain rust + cargo than the old C + autotools mess.

And yet, exa is deprecated :-)

Re: Exa Is Deprecated

#47
post #23
post #13

I never used exa as a general `ls` replacement, but I did use it as a `tree` replacement. Its tree view that gives you file stats from ls alongside a `tree`-like view I haven't found replicated in any other tool. Here are the aliases I use: et() { exa -alT --git -I'.git|node_modules|.mypy_cache|.pytest_cache|.venv' --color=always "$@" | less -R; } alias et1='et -L1' alias et2='et -L2' alias et3='et -L3' exa never han…

Maybe use broot ? Its tree view is its main feature and it handles gitignore and shows many stats including dir sizes. https://dystroy.org/broot/ You can use it just like the original tree tool too: https://dystroy.org/broot/tricks/#replace-tree (disclaimer: broot author)

Thanks for your comment. I have broot installed, but it never sticks in my workflow. I didn't know you could use it as a tree replacement like that, adding file stats & exiting.

It almost works to replace the way I use exa tree, with these caveats:

- I want to not have it elide files ("7 unlisted") at each level. I have my et1, et2, etc. aliases to customize how many levels of detail I get with exa's tree replacement, and then I scroll that with my pager.

- I want it to support LS_COLORS so the files look the same as they do in `ls`

- I want the git status display that exa gives (eg. it shows I if the file is ignored).

- is it possible to customize the order in which the stats are shown? It'd be nice if they match ls more closely. Exa feels like `ls` with extra colors and a tree, broot feels different.

Re: Exa Is Deprecated

#48
post #11
post #2

I hope that the author Benjamin Sago is alright. It's always concerning when FOSS developers disappear for a while - even though it isn't uncommon.

I wish there was a better way for the community to handle this situation without the original author doing what we see here. Sometimes the original author dies unexpectedly for example and it's very hard to salvage the work into a maintained fork. I wrote about this in 2018: https://kodare.net/2018/06/25/salvaging-abandoned-projects.h...

You can set a successor in your GitHub settings: https://docs.github.com/github/setting-up-and-managing-your-...

That successor will gain access to the _public_ repos of your account after presenting a death certificate. As it's only for public repositories, it's a no-brainer for me.

Re: Exa Is Deprecated

#49
Yet another example of why I don't trust any software that markets itself as "modern". In another 20 years, ls will still work perfectly fine.

Re: Exa Is Deprecated

#50

exa: 8 years, dead ls: 38 years and counting. Long live ls.

pneumatic drill: 8 years, dead

the sharp stick of metal my dad gave me: 38 years and counting

long live the sharp stick of metal ?

What a terrible take. Yes, ls is maintained. Although, maintained is a very strong word. It exists. It's getting a few maintenance commits here and there, and in the mean time, it's feature done. It won't evolve anymore. Just like how exa will keep existing, and won't evolve anymore. Exa also does a hell of a lot more than ls, so will LSD, Eza and others. But keep using the sharp stick of metal if it makes you feel better.

Post reply on HN