Skip to content

exa is unmaintained, please use the active fork eza instead #1243

Description

@ariasuni

exa is unmaintained, please use the active fork eza instead.

A lot of work has already been put into it by other people, and I’ll be porting my ongoing work to this fork. Sadly, @ogham seems unreachable so I can’t really archive the project… for now, I’ll redirect people to eza, from the README and issues page.

A page is turning for me: it was great maintaining exa on my own for a while but it wasn’t sustainable and I was in burnout, I’m so glad people finally created a fork that I could contribute to instead of having to handle the whole thing.

Activity

  1. pinned this issue on Sep 5, 2023
  2. Aehmlo commented on Sep 5, 2023

    @Aehmlo

    Second occurrence of exa in the current title should probably read eza?

  3. kohane27 commented on Sep 6, 2023

    @kohane27

    Thank you so much for keeping us updated on the situation. I'm sure we all appreciate your effort to keep this project going! <3

  4. changed the title [-]exa is unmaintained, please use the active fork exa instead[/-] [+]exa is unmaintained, please use the active fork eza instead[/+] on Sep 6, 2023
  5. ariasuni commented on Sep 6, 2023

    @ariasuni
    CollaboratorAuthor

    Second occurrence of exa in the current title should probably read eza?

    Thanks, fixed the typo x)

  6. added a commit that references this issue on Sep 6, 2023
  7. rugk commented on Sep 6, 2023

    @rugk

    You can archive this repository, to mark it as unmaintained. People then cannot submit PRs and there is a big warning that this is archived.

    IMHO this would make it more obvious this is not maintained anymore.

    Edit: Oh sorry just read your OP, forget it, you said that there already.

    Anyway, thanks for maintaining it so long! 🤗

  8. added a commit that references this issue on Sep 7, 2023
  9. added a commit that references this issue on Sep 7, 2023
  10. added a commit that references this issue on Sep 7, 2023
  11. nikelborm commented on Sep 8, 2023

    @nikelborm

    @ariasuni just an idea: send unified instruction how to move PRs to new repo as comments of currently open PRs in this repo

  12. 51 remaining items

  13. 54853315 commented on Oct 28, 2024

    @54853315

    What happend to him @ogham?

  14. ariasuni commented on Nov 1, 2024

    @ariasuni
    CollaboratorAuthor

    No idea, I didn’t hear from him since 2021-04-03, but his website is still up. Last activity from his part I can find online is a retweet on twitter dot com of a post from 2022-07-06.

  15. nikelborm commented on Nov 2, 2024

    @nikelborm

    The last activity I was able to find were 12th June 2023 and 9th June 2023

    https://git.sr.ht/~ogham/bugbear-go/commit/e9375fd8bdba2627ec400b2ec6869186a5bca1ad
    https://git.sr.ht/~ogham/doom/commit/429ecca9db91a07752b95e2363c3af10a92ad394

    Website's certificate was issued Wednesday, August 14, 2024 at 1:54:55 PM although probably been done automatically by certbot.

  16. brent-lidstone commented on Feb 13, 2025

    @brent-lidstone

    Id just like to say, as someone who just found this tool, I think its quite strange that a project owner and leader would just completely ghost a community with 155 other contributors and 24k Github stars, without even so much as sending a response telling people that they don't feel like leading the project anymore. I mean there's nothing wrong with wanting to quit the project, but its another thing entirely to just ghost the rest of the team and not even respond their messages.

  17. verheyenkoen commented on Feb 13, 2025

    @verheyenkoen

    Id just like to say, as someone who just found this tool, I think its quite strange that a project owner and leader would just completely ghost a community with 155 other contributors and 24k Github stars, without even so much as sending a response telling people that they don't feel like leading the project anymore. I mean there's nothing wrong with wanting to quit the project, but its another thing entirely to just ghost the rest of the team and not even respond their messages.

    I'm not sure but I'm afraid you are failing to consider that the maintainer may be deceased. I don't see any activity on their GitHub or Twitter and their website is gone.

  18. ariasuni commented on Feb 14, 2025

    @ariasuni
    CollaboratorAuthor

    I'm not sure but I'm afraid you are failing to consider that the maintainer may be deceased. I don't see any activity on their GitHub or Twitter and their website is gone.

    I’ve long felt it could be a possibility. I just sent him an e-mail (his mail server, on the same domain as his website, still seem to be working), and I also contacted the company listed on his profile. I’ll keep you posted if I get any news.

    For the record, I met him at a RustFest, I think the Zürich one in 2017, but maybe the Paris one in 2018, even thought we barely spoke. I felt proud that he valued my contributions enough, to later gave me the right to commit and merge on his “first real open-source project” (his words), and trusted me to respect his vision for his project.

  19. tshepang commented on Feb 14, 2025

    @tshepang

    Id just like to say, as someone who just found this tool, I think its quite strange that a project owner and leader would just completely ghost a community with 155 other contributors and 24k Github stars, without even so much as sending a response telling people that they don't feel like leading the project anymore. I mean there's nothing wrong with wanting to quit the project, but its another thing entirely to just ghost the rest of the team and not even respond their messages.

    they gave a gift to the world, and in a form that could be kept maintained by someone else (see eza)... whatever the reason for them going abruptly absent, I feel they should be given more grace than this accusation

  20. eggbean commented on Feb 17, 2025

    @eggbean

    I remember wondering about this and I think I found that after some time he stopped committing to GitHub he made a blog post or something like that which suggested travel. I reckon he's got fed up with tech and become spiritual somewhere and has probably become a monk. I've been thinking of doing something like that myself.

  21. nikelborm commented on Feb 17, 2025

    @nikelborm
  22. brent-lidstone commented on Feb 19, 2025

    @brent-lidstone

    Most things I can find online seem to suggest he is not dead. I was literally just pointing out that it's strange to disappear without even sending a message (assuming he has not passed away), and you seem to think that's somehow slandering him directly. I'm sorry if I came across that way. I can find other people online saying something very similar to what I just said:

    There’s a ray of hope on their RSS feed: https://bsago.me/tech-notes/feed.json

    The last published date is September 2022, which is almost a year after their last GitHub activity: https://github.com/ogham?tab=overview&from=2021-12-01&to=202...

    So in absence of other information, I’d rather believe they’re ok. I’ve gone through periods of my life where I blow off all existing responsibilities and reinvent myself. A big project like exa comes with a lot of responsibilities that don’t become apparent until it explodes in popularity; it’s understandable for people to want to disassociate from those.

    Some might argue that open source authors have a responsibility to communicate status, but it seems like Benjamin fulfilled that by making sure exa had additional maintainers that could update the readme with a deprecation notice.

    One other strange phenomenon is that when you run from a responsibility, it can feel like more and more of a hurdle to come back and face it, at least for me. So it’s probably best to assume they’re fine and to put as little pressure on them as possible. Even just popping in to say “I’m still alive” can feel like pressure.

    https://news.ycombinator.com/item?id=37416814

  23. nikelborm commented on Aug 17, 2026

    @nikelborm

    The last activity I was able to find was on 12th June 2023 and 9th June 2023

    https://git.sr.ht/~ogham/bugbear-go/commit/e9375fd8bdba2627ec400b2ec6869186a5bca1ad
    https://git.sr.ht/~ogham/doom/commit/429ecca9db91a07752b95e2363c3af10a92ad394

    Website's certificate was issued Wednesday, August 14, 2024 at 1:54:55 PM although probably been done automatically by certbot.

    What's interesting is that the repos are not available now, but this isn't caused by some inactive account deletion policy; on the contrary, the account is still in place: https://sr.ht/projects/~ogham/.

  24. cyqsimon commented on Oct 10, 2026

    @cyqsimon

    I was cleaning up my local repos today when I came across one of yours. Wherever you are and whatever you are up to, I hope you are doing well 🙂.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions