#oilshell — Public Fediverse posts

@simonmic Not sure about #oilshell though. I'm very happy with #fishshell for interactive use and when there's a need for advanced scripting, why not use python or javascript directly?

@simonmic Not sure about #oilshell though. I'm very happy with #fishshell for interactive use and when there's a need for advanced scripting, why not use python or javascript directly?

@simonmic Not sure about #oilshell though. I'm very happy with #fishshell for interactive use and when there's a need for advanced scripting, why not use python or javascript directly?

@simonmic Not sure about #oilshell though. I'm very happy with #fishshell for interactive use and when there's a need for advanced scripting, why not use python or javascript directly?

@simonmic Not sure about #oilshell though. I'm very happy with #fishshell for interactive use and when there's a need for advanced scripting, why not use python or javascript directly?

http://yosemitesam.ch/3-tools-for-2025/

Recommends #oilshell, #radicle, and #simplexchat for 2025.
Discussion: https://news.ycombinator.com/item?id=42904966

http://yosemitesam.ch/3-tools-for-2025/

Recommends #oilshell, #radicle, and #simplexchat for 2025.
Discussion: https://news.ycombinator.com/item?id=42904966

http://yosemitesam.ch/3-tools-for-2025/

Recommends #oilshell, #radicle, and #simplexchat for 2025.
Discussion: https://news.ycombinator.com/item?id=42904966

http://yosemitesam.ch/3-tools-for-2025/

Recommends #oilshell, #radicle, and #simplexchat for 2025.
Discussion: https://news.ycombinator.com/item?id=42904966

http://yosemitesam.ch/3-tools-for-2025/

Recommends #oilshell, #radicle, and #simplexchat for 2025.
Discussion: https://news.ycombinator.com/item?id=42904966

Oil updates are always as interesting read for shell nerds https://www.oilshell.org/blog/2024/12/objects.html

#ShellScript #OilShell

Oil updates are always as interesting read for shell nerds https://www.oilshell.org/blog/2024/12/objects.html

#ShellScript #OilShell

Oil updates are always as interesting read for shell nerds https://www.oilshell.org/blog/2024/12/objects.html

#ShellScript #OilShell

Oil updates are always as interesting read for shell nerds https://www.oilshell.org/blog/2024/12/objects.html

#ShellScript #OilShell

Oil updates are always as interesting read for shell nerds https://www.oilshell.org/blog/2024/12/objects.html

#ShellScript #OilShell

osh alone is already worthwhile and succeeding. It also unlocks the way forward - without osh, neither ysh or any other new shell language can ever really get traction. With osh’s support for gradual cleanup, it's possible.

(cc from the #oilshell reddit)

2/

osh alone is already worthwhile and succeeding. It also unlocks the way forward - without osh, neither ysh or any other new shell language can ever really get traction. With osh’s support for gradual cleanup, it's possible.

(cc from the #oilshell reddit)

2/

osh alone is already worthwhile and succeeding. It also unlocks the way forward - without osh, neither ysh or any other new shell language can ever really get traction. With osh’s support for gradual cleanup, it's possible.

(cc from the #oilshell reddit)

2/

osh alone is already worthwhile and succeeding. It also unlocks the way forward - without osh, neither ysh or any other new shell language can ever really get traction. With osh’s support for gradual cleanup, it's possible.

(cc from the #oilshell reddit)

2/

osh alone is already worthwhile and succeeding. It also unlocks the way forward - without osh, neither ysh or any other new shell language can ever really get traction. With osh’s support for gradual cleanup, it's possible.

(cc from the #oilshell reddit)

2/

I'm a longtime bash user using osh as my default shell for a year or so now, with only minor noticeable issues. I haven't yet had a need to invest time in the still-being-designed ysh.
I feel osh is the killer feature of the Oils project - 1. a truly compatible, cleaned up, principled bash replacement, with 2. optional knobs you can turn to gain more correctness and power, and 3. the promise of easy interop or migration to the next-gen ysh language, providing future-proofness.

#oilshell

I'm a longtime bash user using osh as my default shell for a year or so now, with only minor noticeable issues. I haven't yet had a need to invest time in the still-being-designed ysh.
I feel osh is the killer feature of the Oils project - 1. a truly compatible, cleaned up, principled bash replacement, with 2. optional knobs you can turn to gain more correctness and power, and 3. the promise of easy interop or migration to the next-gen ysh language, providing future-proofness.

#oilshell

I'm a longtime bash user using osh as my default shell for a year or so now, with only minor noticeable issues. I haven't yet had a need to invest time in the still-being-designed ysh.
I feel osh is the killer feature of the Oils project - 1. a truly compatible, cleaned up, principled bash replacement, with 2. optional knobs you can turn to gain more correctness and power, and 3. the promise of easy interop or migration to the next-gen ysh language, providing future-proofness.

#oilshell

I'm a longtime bash user using osh as my default shell for a year or so now, with only minor noticeable issues. I haven't yet had a need to invest time in the still-being-designed ysh.
I feel osh is the killer feature of the Oils project - 1. a truly compatible, cleaned up, principled bash replacement, with 2. optional knobs you can turn to gain more correctness and power, and 3. the promise of easy interop or migration to the next-gen ysh language, providing future-proofness.

#oilshell

I'm a longtime bash user using osh as my default shell for a year or so now, with only minor noticeable issues. I haven't yet had a need to invest time in the still-being-designed ysh.
I feel osh is the killer feature of the Oils project - 1. a truly compatible, cleaned up, principled bash replacement, with 2. optional knobs you can turn to gain more correctness and power, and 3. the promise of easy interop or migration to the next-gen ysh language, providing future-proofness.

#oilshell

The #oils:matrix.org chat room I started last year, for matrix users to chat about #oilshell, is still an undiscovered secret. But I think it'll grow eventually, and I hope so because Zulip just isn't as easy!

The #oils:matrix.org chat room I started last year, for matrix users to chat about #oilshell, is still an undiscovered secret. But I think it'll grow eventually, and I hope so because Zulip just isn't as easy!

The #oils:matrix.org chat room I started last year, for matrix users to chat about #oilshell, is still an undiscovered secret. But I think it'll grow eventually, and I hope so because Zulip just isn't as easy!

The #oils:matrix.org chat room I started last year, for matrix users to chat about #oilshell, is still an undiscovered secret. But I think it'll grow eventually, and I hope so because Zulip just isn't as easy!

The #oils:matrix.org chat room I started last year, for matrix users to chat about #oilshell, is still an undiscovered secret. But I think it'll grow eventually, and I hope so because Zulip just isn't as easy!

Back from outing: getting out of #fishshell is really hard. Tried going back to #bash (even with #blesh), tried #OilShell and none of them really work (filed bug reports). Sad. Anybody knows about POSIX-compatible interactive shell which actually works and at least from distance can compete with fish?

Back from outing: getting out of #fishshell is really hard. Tried going back to #bash (even with #blesh), tried #OilShell and none of them really work (filed bug reports). Sad. Anybody knows about POSIX-compatible interactive shell which actually works and at least from distance can compete with fish?

Back from outing: getting out of #fishshell is really hard. Tried going back to #bash (even with #blesh), tried #OilShell and none of them really work (filed bug reports). Sad. Anybody knows about POSIX-compatible interactive shell which actually works and at least from distance can compete with fish?

Back from outing: getting out of #fishshell is really hard. Tried going back to #bash (even with #blesh), tried #OilShell and none of them really work (filed bug reports). Sad. Anybody knows about POSIX-compatible interactive shell which actually works and at least from distance can compete with fish?

Back from outing: getting out of #fishshell is really hard. Tried going back to #bash (even with #blesh), tried #OilShell and none of them really work (filed bug reports). Sad. Anybody knows about POSIX-compatible interactive shell which actually works and at least from distance can compete with fish?

@bean Lately, #oilshell , which I have started daily driving on Ubuntu, and am working on a build for for FreeBSD.

See more at https://www.oilshell.org and particularly https://www.oilshell.org/blog/2021/01/why-a-new-shell.html

The goal of the project is to build a shell compatible with bash (osh), bust statically parsed and with an upgrade path to a much more powerful shell language (ysh), which improves on the warts of Bourne-lineage shells.

@bean Lately, #oilshell , which I have started daily driving on Ubuntu, and am working on a build for for FreeBSD.

See more at https://www.oilshell.org and particularly https://www.oilshell.org/blog/2021/01/why-a-new-shell.html

The goal of the project is to build a shell compatible with bash (osh), bust statically parsed and with an upgrade path to a much more powerful shell language (ysh), which improves on the warts of Bourne-lineage shells.

@bean Lately, #oilshell , which I have started daily driving on Ubuntu, and am working on a build for for FreeBSD.

See more at https://www.oilshell.org and particularly https://www.oilshell.org/blog/2021/01/why-a-new-shell.html

The goal of the project is to build a shell compatible with bash (osh), bust statically parsed and with an upgrade path to a much more powerful shell language (ysh), which improves on the warts of Bourne-lineage shells.

@bean Lately, #oilshell , which I have started daily driving on Ubuntu, and am working on a build for for FreeBSD.

See more at https://www.oilshell.org and particularly https://www.oilshell.org/blog/2021/01/why-a-new-shell.html

The goal of the project is to build a shell compatible with bash (osh), bust statically parsed and with an upgrade path to a much more powerful shell language (ysh), which improves on the warts of Bourne-lineage shells.

@bean Lately, #oilshell , which I have started daily driving on Ubuntu, and am working on a build for for FreeBSD.

See more at https://www.oilshell.org and particularly https://www.oilshell.org/blog/2021/01/why-a-new-shell.html

The goal of the project is to build a shell compatible with bash (osh), bust statically parsed and with an upgrade path to a much more powerful shell language (ysh), which improves on the warts of Bourne-lineage shells.

I've fallen down the rabbit hole over at Andy Chu's blog for #oilshell: https://www.oilshell.org/blog/

Learned some #shell patterns that I was able to use immediately

"$0" dispatch: https://www.oilshell.org/blog/2021/08/xargs.html#xargs-can-invoke-shell-functions-with-the-0-dispatch-pattern

Used that to build a helper function to make `mv` `xargs`-friendly (i.e., don't call once per file)

move () {
d="$1"
shift
mv "$@" "$d"
}

move_many () {
find . |
filter |
xargs "$0" move /dest/dir
}

This feels like it rhymes with currying, but with variadic functions. Very cool.

I've fallen down the rabbit hole over at Andy Chu's blog for #oilshell: https://www.oilshell.org/blog/

Learned some #shell patterns that I was able to use immediately

"$0" dispatch: https://www.oilshell.org/blog/2021/08/xargs.html#xargs-can-invoke-shell-functions-with-the-0-dispatch-pattern

Used that to build a helper function to make `mv` `xargs`-friendly (i.e., don't call once per file)

move () {
d="$1"
shift
mv "$@" "$d"
}

move_many () {
find . |
filter |
xargs "$0" move /dest/dir
}

This feels like it rhymes with currying, but with variadic functions. Very cool.

I've fallen down the rabbit hole over at Andy Chu's blog for #oilshell: https://www.oilshell.org/blog/

Learned some #shell patterns that I was able to use immediately

"$0" dispatch: https://www.oilshell.org/blog/2021/08/xargs.html#xargs-can-invoke-shell-functions-with-the-0-dispatch-pattern

Used that to build a helper function to make `mv` `xargs`-friendly (i.e., don't call once per file)

move () {
d="$1"
shift
mv "$@" "$d"
}

move_many () {
find . |
filter |
xargs "$0" move /dest/dir
}

This feels like it rhymes with currying, but with variadic functions. Very cool.

I've fallen down the rabbit hole over at Andy Chu's blog for #oilshell: https://www.oilshell.org/blog/

Learned some #shell patterns that I was able to use immediately

"$0" dispatch: https://www.oilshell.org/blog/2021/08/xargs.html#xargs-can-invoke-shell-functions-with-the-0-dispatch-pattern

Used that to build a helper function to make `mv` `xargs`-friendly (i.e., don't call once per file)

move () {
d="$1"
shift
mv "$@" "$d"
}

move_many () {
find . |
filter |
xargs "$0" move /dest/dir
}

This feels like it rhymes with currying, but with variadic functions. Very cool.

I've fallen down the rabbit hole over at Andy Chu's blog for #oilshell: https://www.oilshell.org/blog/

Learned some #shell patterns that I was able to use immediately

"$0" dispatch: https://www.oilshell.org/blog/2021/08/xargs.html#xargs-can-invoke-shell-functions-with-the-0-dispatch-pattern

Used that to build a helper function to make `mv` `xargs`-friendly (i.e., don't call once per file)

move () {
d="$1"
shift
mv "$@" "$d"
}

move_many () {
find . |
filter |
xargs "$0" move /dest/dir
}

This feels like it rhymes with currying, but with variadic functions. Very cool.

(In future, if osh/ysh get some make/just-inspired features or libraries (seems quite possible), the pendulum may swing back to using shell only.

#oilshell #justfile #makefile

(In future, if osh/ysh get some make/just-inspired features or libraries (seems quite possible), the pendulum may swing back to using shell only.

#oilshell #justfile #makefile

(In future, if osh/ysh get some make/just-inspired features or libraries (seems quite possible), the pendulum may swing back to using shell only.

#oilshell #justfile #makefile

(In future, if osh/ysh get some make/just-inspired features or libraries (seems quite possible), the pendulum may swing back to using shell only.

#oilshell #justfile #makefile

after a day of playing around with all #linux shells:

- #xonsh is awesome but a bit clunky
- #nushell is great, will probably be my runner
- #marcel very similar to nushell but treats everything as a Python objects instead of tables. Will come back to this one. No #nix install yet.
- #fish as good as it gets for classic shells
- #zsh, #bash - no real reason to run it unless you're locked into bash ecosystem
- #oilshell - couldn't get it to work but there's a lot of good work here. Next time.