Output success error codes in unexpected range (see: robocopy).
Use special characters to try TUI things but leave the buffer in weird states.
Have many input params, and default to the most useless ones when nothing is passed. Make some params unnecessarily required.
Go on very long tangents for no reason in the manpage, but keep your -h message as just the list of badly named params.
Use stderr as your stdout.
---- I present to you worse-cat:
wcat notes.txt
error: --encoding is required. Exiting.
wcat --encoding=utf-8 notes.txt
┌─────────────────────────────────┐
│ About to display: notes.txt │
│ Are you sure? [y/N/maybe]: │
└─────────────────────────────────┘
y
stdout: ≈3 paragraphs
stderr: [file content]
echo $?
212
(I'll save you the manpage and worse-ls)
I instantly recalled a site from this era and amazeballs it’s still there! Superbad.com All hail!
so linux is already there
In terms of usability, moving to FreeBSD from Linux is quite a positive experience. Pity that hardware and software support is limited on the BSDs.
Results from ls would be a few sentences explaining the types of files in the directory. Add a -l on there and it will give you a general overview of the permissions and size of the files. Ex. “These are rather large files that are primarily, but not exclusively, limited to root.”
Results from cat would give a summary of the file. You’d get the same results, with some degree of randomness from more and less as well.
Using any command with sudo would provide the same type of results, but in all caps.
Trying to pipe commands together would be a slop multiplier.