3 ms·

Unix Shell Programming: The Next 50 Years – HotOS Xviii [pdf]

3 points by smasher164 5y ago

mikece 5y ago
It would be interesting to see less reliance on the regex parsing of bash shell command responses and a move toward something like PowerShell where the return of all commands is an object, the properties of which can be accessed with familiar dot notion (and enumerating with a foreach or lambda equivalent). I find it ironic that after creating such a powerful upgrade on the concept of a shell scripting language that Microsoft then enabled -- and even promotes -- the use of bash on Windows for systems administration.
- flas9sd 5y ago
  true. Increasingly commands can output their return as json, but then jq is also not as easy to handle as I sometimes wish. Maybe oils "quoted string notation" (QSN) for safer passing of strings can be of interest to you: http://www.oilshell.org/blog/2020/10/osh-features.html#safe-processing-of-user-supplied-data-like-filenames http://www.oilshell.org/blog/2020/10/osh-features.html#safe-... Concerning Powershell the author of oilshell addresses how shells are native to their surroundings in http://www.oilshell.org/blog/2021/01/philosophy-design.html#situated-languages-powershell-vs-oil http://www.oilshell.org/blog/2021/01/philosophy-design.html#... - he'll be attending the HotOS panel too. Implementing WSL2, native openssh in Windows, the use of bash, it must be to stay relevant. Edit: and I think this thread will interest you too - https://lobste.rs/s/k10sfa/why_did_i_write_my_programming_projects#c_mnauw8 https://lobste.rs/s/k10sfa/why_did_i_write_my_programming_pr... and the sustrik/uxy reference within
- majkinetor 5y ago
  You can't simply ignore bash - while I would like nothing more then to never touch it again, the fact is that giant pool of scripts is created and just the same as with Cobol, they will persists for a long time. What I would like to see is PowerShell becoming default in more and more distros. The only problem to achieve that is today making its performance better.

3 points by smasher164 5y ago

It would be interesting to see less reliance on the regex parsing of bash shell command responses and a move toward something like PowerShell where the return of all commands is an object, the properties of which can be accessed with familiar dot notion (and enumerating with a foreach or lambda equivalent). I find it ironic that after creating such a powerful upgrade on the concept of a shell scripting language that Microsoft then enabled -- and even promotes -- the use of bash on Windows for systems administration.

flas9sd 5y ago
true. Increasingly commands can output their return as json, but then jq is also not as easy to handle as I sometimes wish. Maybe oils "quoted string notation" (QSN) for safer passing of strings can be of interest to you: http://www.oilshell.org/blog/2020/10/osh-features.html#safe-processing-of-user-supplied-data-like-filenames http://www.oilshell.org/blog/2020/10/osh-features.html#safe-... Concerning Powershell the author of oilshell addresses how shells are native to their surroundings in http://www.oilshell.org/blog/2021/01/philosophy-design.html#situated-languages-powershell-vs-oil http://www.oilshell.org/blog/2021/01/philosophy-design.html#... - he'll be attending the HotOS panel too. Implementing WSL2, native openssh in Windows, the use of bash, it must be to stay relevant. Edit: and I think this thread will interest you too - https://lobste.rs/s/k10sfa/why_did_i_write_my_programming_projects#c_mnauw8 https://lobste.rs/s/k10sfa/why_did_i_write_my_programming_pr... and the sustrik/uxy reference within
majkinetor 5y ago
You can't simply ignore bash - while I would like nothing more then to never touch it again, the fact is that giant pool of scripts is created and just the same as with Cobol, they will persists for a long time. What I would like to see is PowerShell becoming default in more and more distros. The only problem to achieve that is today making its performance better.