←back to thread

lsr: ls with io_uring

(rockorager.dev)
335 points mpweiher | 5 comments | | HN request time: 0.001s | source
Show context
danbruc ◴[] No.44604591[source]
Why does this require inventing lsr as an alternative to ls instead of making ls use io_uring? It seems pretty annoying to have to install replacements for the most basic command line tools. And especially in this case, where you do not even do it for additional features, just for getting the exact same thing done a bit faster.
replies(6): >>44604637 #>>44604660 #>>44604674 #>>44604716 #>>44605151 #>>44605208 #
nailer ◴[] No.44604637[source]
`ls` is in C, `lsr` is in Zig. The `lsr` programmer probably doesn't want to make new code in C.
replies(1): >>44604705 #
loeg ◴[] No.44604705[source]
In addition, the author might not want to sign away their rights to the FSF.
replies(2): >>44604768 #>>44604946 #
1. andrepd ◴[] No.44604946[source]
What on earth are you talking about? Why would this be the case?
replies(2): >>44604993 #>>44605768 #
2. scott_w ◴[] No.44604993[source]
Depending on the implementation (and I don't know which `ls` is being referred to), modifying `ls` might mean modifying an FSF project which require copyright assignment as a condition of patch submissions.
replies(1): >>44608596 #
3. loeg ◴[] No.44605768[source]
Are you unfamiliar with contributing to GNU projects (ls is part of GNU corutils)?

https://www.gnu.org/prep/maintain/maintain.html#Copyright-Pa...

4. leni536 ◴[] No.44608596[source]
That's only the case if the author would want to upstream their changes. If they wanted to only fork ls then they would only be required to comply with the license, without assigning copyright over.
replies(1): >>44609134 #
5. scott_w ◴[] No.44609134{3}[source]
That may be the case but then why bother modifying ls when you can just write your own exactly as you want it?