6 ms·
Oil 0.14.2 – Interactive Shell, and Conceding to autoconf
- elteto 4y agoWe're also starting to use the "Oils for Unix" name. Can’t wait for the book “Essential Oils for Unix” to come out.
- chubot 4y agoSounds like something we need :) If you want a picture in your head, the Unix Magic Poster isn't a bad one :) https://jpmens.net/2021/04/09/the-unix-magic-poster/ https://jpmens.net/2021/04/09/the-unix-magic-poster/
- seanw444 4y agoI've seen Oil mentioned here and there, and haven't thought much of it. But this blog is pretty interesting and really shows the effort put into it. I may have to give it a whirl.
- chubot 4y agoGlad to hear it, feel free to post results / feedback on Zulip! On #oil-help or #oil-discuss-public, etc.
- 0cf8612b2e1e 4y agoReal shame about having to give into the bad eval behavior. I am honestly surprised the project has been able to enable any strictness at all. I assumed any and all bad shell behavior had been utilized somewhere.
- chubot 4y ago(author here) Just to be clear for other readers, we still avoid the dangerous behavior while allowing the (arguably confusing) behavior that autoconf requires. And this only changes OSH, not YSH / Oil, which is still statically parsed. It's true that most of the strictness has become opt-in rather than opt-out, but it's still there! So you can choose it if you want. The Oil language / YSH is basically just OSH, with a bunch of strict options and new features on top (with new syntax)! Surprisingly, that's enough to make it a brand new language.
- 0xblood 4y agoFirst time I hear about oil shell. Funny name, but that aside, I have a hard time taking a shell seriously that started out written in python. They describe it as having "python-like types", interesting. And they say it's a shell targeted at people who "write scripts, which may get into the hundreds or even thousands of lines" rather than end-users. If you write complex scripts, please use a proper language. Also, I've been writing "complex" bash scripts since ages, and of course it can be somewhat annoying with bash's quirks. But it runs almost everywhere without extra dependencies, which is the main reason I use it. If I had to install oil on all machines running my scripts, why wouldn't I go ahead and use rather go and distribute binaries? Well, my guess is this will never catch on.
- wodenokoto 4y agoThis made me more confused about what oil is. I thought it was a shell that competes with bash but doesn’t try to be strictly posix. Now there’s oil language, OSH and oil for Unix?
- chubot 4y ago(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_conceding#c_us3r6x https://lobste.rs/s/qrbcue/oil_0_14_2_interactive_shell_conc...
- Arcuru 4y agoI 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 https://github.com/oilshell/oil/wiki
- chubot 4y agoThanks 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 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)