It will definitely be the only utility I recall that uses a numeral.
- https://pubs.opengroup.org/onlinepubs/9699919799/idx/utilities.html
Note that many versions of macOS adhere to these standards: https://www.opengroup.org/openbrand/register/ https://www.opengroup.org/openbrand/register/brand3700.htm https://www.opengroup.org/openbrand/register/brand3705.htm
I know it had been this way for decades and was grandfathered in as a feature
If people were more resistant to “grandfathered” features I think we would not have as much software as we do today: https://www.jwz.org/doc/worse-is-better.html https://en.wikipedia.org/wiki/Worse_is_better
provide about 50%–80% of what you want from an operating system
one expects that if the 50% functionality Unix and C support is satisfactory, they will start to appear everywhere.
Unix and C are the ultimate computer viruses.
users have already been conditioned to accept worse than the right thing.
It’s probably possible to make several programs with “50% functionality” in the time it takes to make one program with 100% functionality. Having more programs that are suitable for a majority of relevant applications is probably better than having one program that is suitable for all relevant applications, since having more programs will probably enable a larger variety of problems to be solved, and people often have to solve many different types of problems in their life.
what does usr mean
https://refspecs.linuxfoundation.org/fhs.shtml https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04.html
Some operating systems may handle long path or file names in a surprising way, so having short paths and names is useful: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_13
If any pathname component is longer than {NAME_MAX}, the implementation shall consider this an error.
if the combined length exceeds {PATH_MAX}, and the implementation considers this to be an error, pathname resolution shall fail
{NAME_MAX}
and {PATH_MAX}
are described in more detail at https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html#tag_13_23_03_02 and used in the context of https://pubs.opengroup.org/onlinepubs/9699919799/utilities/pathchk.html
Note
The resources I linked are descriptive and not prescriptive, but in my experience they are suitable to depend upon as a reliable baseline, which makes meeting client requirements with software engineering easier.
I think this is not among the most important things to be talking about.
https://www.hsph.harvard.edu/magazine/magazine_article/fluoridated-drinking-water/
https://nutritionsource.hsph.harvard.edu/fluoride/
https://duckduckgo.com/?t=ftsa&q=fluoride+site%3A.edu&ia=web