Carrots

Why should anyone use OSH over bash?

• Removed many warts (e.g. with arrays and arithmetic) while still maintaining high compatibility

  • Added options like set -o strict-array for even better behavior (sacrificing compatibility)

• Better parse time and runtime error messages. The infrastructure is there, but it needs more polish.

• More accurate interactive completion (TODO: link to post describing this)

• Shell crash dumps. Implemented with OSH_CRASH_DUMP_DIR but not documented / deployed.

• Lower latency with coprocesses. Prototyped, but not yet in OSH.

• Minor: OSH has a repr builtin which may aid in debugging.

• Simpler configuration: a single ~/.config/oil/oshrc file.

  • No rat's nest of startup files. Easier to put in a dotfiles repo.

Maybe:

• In addition to crash dumps, potentially better tracing (set -x and $PS4).

Not implemented:

• Portable .rc files? To solve the admin problem on remote servers.
• Migration path to a better language: Oil!
  • Could write inline function calls and expressions, e.g. echo $f(x, y)

Oil Carrots

It's too early for this since it isn't implemented :-/ There are some potential benefits listed on Why Create a New Unix Shell?