Wtf is "semi-done"?

There is "done" and there is "not done"...

I imagine "semi-done" means "works enough that it can be dogfooded by the devs and tried out by the curious among us, but does not exactly mirror behaviour of GNU cp in terms of corner cases and error output".

I think we need to be more flexible than classifying things as done/not-done. Even GNU coreutils has open issues[0] - is it "done" or "not done"?

[0] = https://debbugs.gnu.org/cgi/pkgreport.cgi?pkg=coreutils

If that's how you categorize software, then no software has ever been "done". There are always new cases, bugs, features, and performance improvements. You will never run out of any one of those things.

In this case, semi-done probably means what it usually means: some common cases are handled, while others aren't yet.

if you believe that, there is not a single piece of done software in the world, besides perhaps tex.

"semi-done" means:

1. Not done. :-(

2. A lot has been done already, i.e. not just-started.

3. Not almost-done, i.e. there's significant work still to be done

In that case at least one of "done" and "not done" needs to be a spectrum; semi-done is a point on one of those spectra

You think that's confusing? Wait until you hear about half "A" presses.

Portions of code could be completed and others are not? See semifinished.

WIP? Dude, chill… you’re not paying for it