I don't see the difference between osh / olang vs. osh / ysh ? Why is the former clearer than the latter?
Which of the following binaries are associated with the oil project?
A) osh
B) ysh
A probably, not B. Which of the following binaries is associated with bash compatibility?
A) osh
B) ysh
Dunno, they both look like shells. 50/50 random guess on each. Which of the following binaries is used on programs written in the oil language?
A) osh
B) ysh
Dunno, they both look like shells. A) looks like it's related to oil though so maybe that one again.Now flip ysh for olang...
Which of the following binaries are associated with the oil project?
A) osh
B) olang
A and B both seem likely. Which of the following binaries is associated with bash compatibility?
A) osh
B) olang
A is named like shells, probably that. Which of the following binaries is used on programs written in the oil language?
A) osh
B) olang
B about repeats the question back so B, also I'm now doubly sure osh was the bash compatible option in the last question.I'm not saying olang is the right final answer but the name should first try to make sense THEN try to sound clever and ysh/soil both have that backwards as does trying to label both as a shell of the project (even though it's technically correct it's trying to make sense after not first).
I would say that the third question is invalid -- once there is YSH, there is NO MORE "Oil", and no more "Oil language".
The name is just YSH.
I agree there's a slight problem with the first question, using "Oils for Unix".
You might assume that osh is what you should use rather than ysh, because it starts with "O".
But I don't know how to solve that problem :)
I think that simply documenting osh, ysh, and "oils for unix" could be sufficient.
---
One idea I thought of is to rename EVERYTHING.
- ysh could be the compatible shell (formerly osh)
- yam could be the new Python-like language. Problem: Yam isn't googleable, I can't find a better name.
What do you think? Ideas welcome
(FWIW ysh sort of comes from "the shell with hay". Hay is one component of the project.)
One thing to consider is you kind of get 1 “nonsense” pass in that you can really pick anything as the project name long as everything gets named in relation. E.g. hardly anyone knows rust is named after the rust fungus because it’s hardy but everyone gets that rustc is the compiler, rustup updates rust, .rs and .rlib are the file extensions, rust lang refers to the language in particular, and the community makes tons of rust related name puns from there. Oil was actually a really solid option for that kind of base beyond the connotation often being negative.
All of these should be available
- sudo apt-get $PROJECT_NAME
- $PROJECT_NAME.org
- github.com/$PROJECT_NAME
- twitter/$PROJECT_NAME
etc.
Random brainstorming
- OYL
- OYLS
- OYLS for Unix
So you have a "Y" in there for YSH.
But it seems a bit ugly IMO
Few will gain clarity by an old english meaning of "oils" and "old shell"/"young shell" isn't really gaining many favors in searches even versus the infamous "oil shell"/"shell oil" problem. If it's an extended bourne compatible shell everyone is already used to the pattern of sh, ash, and dash/bash so why not just let osh be "oil shell" as people have already been expecting. Instead of "ysh" it could be something like olang (or maybe oilang, but that's a tougher topic because of the l/ll dilemma) for the programming focused incantation? Searches would be "osh shell" and "olang" just like people Google search for "fish shell"/"bash shell" and "golang"/"ziglang" today.
With osh/olang it's clear what each is intended to focus on, they use existing intuitive naming patterns, search patterns match how people already search about shells, having 2 separate incantations nearly explains itself by name, and you don't need to know about the overall "oils" but when you do the differences already makes sense.