Part 2
"I have seen many oil shell posts, but still don’t know what the heck the actual OiL language looks like."
https://lobste.rs/s/uqwaue/oil_success_with_aboriginal_alpine#c_otrg8p
See this thread. I will ignore suggestions without code. (don't be so rude though).
https://www.reddit.com/r/ProgrammingLanguages/comments/7tu30g/why_create_a_new_unix_shell/dthcmbv/
Do you really need 1000+ lines of shell scripts? I almost have 20 years with shell scripting and I still have the rule of not writing longer than 1-2 page shell scripts and use something else for longer projects or break it down to much smaller chunks and invoke the parts with a main.sh.
MAYBE: and if you're going to disrupt existing shells - why would you not use JS? (I don't care for JS, but it is the lingua franca du jour)
See last post. I didn't write those shell scripts. Do you use linux, and do you use the cloud? You rely on them.
This is the motivation for making Oil statically parseable.
There should be a feature to analyze the scripts a binary runs.
TODO:
oil --analyze : this is an easy one
oil --fix oil parse
Or maybe just
print --deps
Specialized skills I want:
Also you can look at the release announcements for contributors, to see what other people are doing.
Add to angry FAQ:
Do you use Unix? Do you use the cloud? You rely on them.
Why not Perl.
shell:
f() { echo -- ls / echo -- }
f > out.txt
f | escape-html > out.txt
proc f { echo -- ls / echo -- }
four answers:
https://www.reddit.com/r/oilshell/comments/7tqs0a/why_create_a_new_unix_shell/dtky61p/
Why not Python could be filled out too:
xargs -P?
Good feedback:
want xargs -P :