News for hackers. Stuff that matters.
Re:Oil 0.14.2 – Interactive Shell, and Conceding to autoconf by chubot on Friday March 17, 2023 @02:19PM (#35200837)
(author here) The next blog post will explain it, and I'll update the home page, but to be short:

OSH - POSIX and bash-compatible shell. (The most bash-compatible shell by a mile!)

YSH (formerly Oil) - new language with Python- and JS-like data structures, Ruby-like blocks. You can upgrade smoothly from OSH to YSH.

"Oils for Unix" (formerly "oilshell") -- the whole project, which includes OSH, YSH, and data serialization languages based on JSON.

The old names were confusing because the project was called Oil, and it also had a part called Oil. People reasonably assumed those were the same thing.

Also there was "OSH", the compatible shell -- but people reasonably thought that just mean "Oil shell". It's all spelled out on the web site, and in the glossary (both of which I will update), but I understand the confusion.

More rationale for renaming here: https://lobste.rs/s/qrbcue/oil_0_14_2_interactive_shell_conc...

Re:Oil 0.14.2 – Interactive Shell, and Conceding to autoconf by Arcuru on Friday March 17, 2023 @02:51PM (#35201263)
I look forward to that blog post, I hope that can clear up some of the confusion.

Personally I found that the best introduction for me to actually understand what the different parts do (mainly OSH and Oil Shell) was the Github wiki, particularly "OSH versus Oil" and the two Migration guide posts. Even reading several of your posts, I didn't fully understand what being "an upgrade path from bash" actually meant until I saw the mechanics of how the process would go, and then it all clicked for me.

I think a guided walkthrough of the "upgrade" process would be very valuable to help people understand what the goal is, and would be a good introduction to the project.

https://github.com/oilshell/oil/wiki

Re:Oil 0.14.2 – Interactive Shell, and Conceding to autoconf by chubot on Friday March 17, 2023 @07:14PM (#35204135)
Thanks for this feedback! I had almost forgotten about that page, which was linked in this post:

http://www.oilshell.org/blog/2021/12/backlog-language.html

I will take your point about walking through the upgrade process. Some things are still not stable so I've been hesitant to "recommend" it, but I think we can just make that clear. Most languages go through a big period of breakages before they get stable

And to be clear OSH is very stable, while YSH isn't. (Next post will also have a list of breaking changes)

Re:Oil 0.14.2 – Interactive Shell, and Conceding to autoconf by zamadatix on Friday March 17, 2023 @11:49PM (#35205867)
I don't mean to sound like a dunce but the naming is very confusing to work out. I've spent an embarrassing amount of time reading the blog posts, glossaries, wiki, and comments and I'm still left a bit confused on the naming choices being the way they are. Part of that may be each explanation tries to teach me about the component in relation the entire project instead of pieces making sense standalone.

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.

Re:Oil 0.14.2 – Interactive Shell, and Conceding to autoconf by chubot on Saturday March 18, 2023 @01:47AM (#35206483)
I agree the naming is confusing, so that's why we're renaming it :)

I don't see the difference between osh / olang vs. osh / ysh ? Why is the former clearer than the latter?

Re:Oil 0.14.2 – Interactive Shell, and Conceding to autoconf by zamadatix on Saturday March 18, 2023 @03:22AM (#35206926)
Imagining being asked the following as if I hadn't read a ton on the project already this is how'd I'd answer:

  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).

Re:Oil 0.14.2 – Interactive Shell, and Conceding to autoconf by chubot on Saturday March 18, 2023 @10:52AM (#35209556)
Thank you for explaining the reasoning -- that helps.

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.)

Re:Oil 0.14.2 – Interactive Shell, and Conceding to autoconf by zamadatix on Saturday March 18, 2023 @12:21PM (#35210357)
Something like ysh and yam seems great as well, assuming ysh then means yam shell and the overall project name is related to yam in some way. I don’t have a better “rename everything” name in mind though, hard to say without a good understanding of the other components.

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.

Re:Oil 0.14.2 – Interactive Shell, and Conceding to autoconf by chubot on Saturday March 18, 2023 @07:39PM (#35214344)
I see your point about connecting the project name to the binary name, but it's going to be hard to find that global name

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