[broodbucket]

I have the opposite feeling about package lethargy, I don't want to remember that exa is now eza at the time that my distro finally gets around to packaging eza, I want to do it now when it's right in front of me.

I'll go try lsd instead (and then I'll try the other ls rewrite, har har)

[perihelions]

Ehh, I guess I'm your opposite. I want to be insulated from exciting upstream developments, especially for stable, boring stuff like coreutils. I want those to be boring. I don't want "exa is now eza" or whatever push-notified to my command line on a random Tuesday.

[KptMarchewa]

I want those to be boring for my scripts; I want modern replacements for my manual use.

[broodbucket]

I guess so, I've been running Arch on most of my servers for the last decade. Sometimes the fragmentation of the ecosystem comes in handy!

[basedrum]

Yet you read hacker news, where you get pushed the latest thing every day

[tlamponi]

The Debian maintainer of the exa package can, and probably will, either:

- just add a backward compat alias

- make eza a transitive dependency so that exa can be sunset cleanly and adds a NEWS file entry that every user will see on upgrade to the version that drops the exa binary.

[post-factum]

In case you are an Arch user, eza is already there.