@Specular
Thanks for the honest, constructive criticism!
First, I want to say you are generally right about the alias entries. It should be with the original entry it refers to.
In the case of arch command (alias to
uname -a), it is a bit of special case, since it is a known command that is be searched for and used by name. It even has its own executable (
arch.exe) with some releases for Windows (see coreutils in Cygwin or MSYS2).
But I can definitely see it go either way. For example, I included
hd in the description of
hexdump. Same with
egrep and fgrep and
Gzip, etc.
----------------------------------------------------------------------------------------------------------
Why add these subcommands as entries:
- It only applies to only those programs like BusyBox of sfk. I think you'd be hard-pressed to find a CLI equivalent for Opera. Even then, Opera is (was ) an "internet suite". There is still a theme connecting its parts.
- These tools are their own tools inside the main executable. They have their own help and syntax independent from the rest.
- They are disparate by design. Even look at the names: one is named after the Swiss Army Knife and the other after the multi-function children's toy!
- These subcommands are usually designed to mimic the function of common/well-known standalone tools.
- A common feature is also that you usually access the function by typing "command subcommand {switches and arguments}". You don't see that very often, and I think it reflects the idea of them being a tool within a tool.
The point for listing the individual is the use cases for different functions without making behemoth entries with giant descriptions and loads of use cases. This aspect definitely needs some work. So do the descriptions. I also direct your attention to
this post.
----------------------------------------------------------------------------------------------------------
Specular wrote: ↑Thu Nov 12, 2020 10:12 pm
I mean, you clearly have personal feelings about the project (and I'd imagine given some other easy to use and free database site you might be using/customizing that for the same purpose) but tbh some of the concepts/goals are contrary to ethos of the primary site and some of the responses to critiques have come across as politely dismissive since you have your own goals formed and are eager to pursue them.
I definitely don't mean to be dismissive. To be honest, I get a kick when someone raises a point that I had already thought about and have at least a possible solution for. I am like, "Aha, I already thought of that! What do you think of my solution?". I don't mean to be dismissive of the
concern itself or the
person.
If anything,
I feel bad when I take a lot of time to write a detailed reply, only for it to be dismissed without showing me what's wrong with my arguments!
For example, you raise the issue of
maintainability. That is a great point. I spent a lot of time mulling over this and to come with a solution that addresses the issue. In this case,
inherited fields! All those child entries automatically get the common details from the parent entry. You only have to edit one!* It is not a new idea at all. Just one that seems to work to me.
Andrew ironed it out with me and now we have a working solution in place!
(*) As for categories/use cases, they
should be individualized. That's the point. Also, they are unlikely to change much after they are done, if at all, unless there are structural changes beyond regular maintenance.
Even votes for the parent item can be inherited by the child entries. I thought whether it is best to just carry over the vote or give a percentage, and how much voting for a child signifies a vote for the parent (the other way around is usually truer), etc.
----------------------------------------------------------------------------------------------------------
One last thing, if you don't want to see child entries in the database, you can easily do that if the filters system I proposed gets implemented. It shouldn't be too hard at all for Andrew to do it
in a simple way, but
I could use your support!