2 ms·

I collected some experiments in that area here (and anyone should feel free to add more, including their own): https://github.com/oilshell/oil/wiki/Interactive

by chubot 6y ago

I collected some experiments in that area here (and anyone should feel free to add more, including their own): https://github.com/oilshell/oil/wiki/Interactive-Shell https://github.com/oilshell/oil/wiki/Interactive-Shell Many of the articles have nice screenshots / animations to give you a feel for what it is. I plan to turn https://www.oilshell.org/ https://www.oilshell.org/ into a library and I hope people will build GUIs around it. There are some UI possibilities that are difficult or impossible unless you have hooks to the shell other than stdin/stdout. https://github.com/oilshell/oil/issues/738 https://github.com/oilshell/oil/issues/738

madhadron 6y ago
So I recently started a job where I'm on Windows, and I've found myself surprisingly enamored of PowerShell. So many of the things that the shell got wrong are done right. The authors wanted to use <, >, etc. as their real meanings, but apparently the early users rebelled at the idea that > was no longer redirect to file. But things that would be nightmares in unix shells, such as going in and adding a new element as the last child of only one of four elements in an XML document (based on its attribute value) are a few lines of code. I still have decades of muscle memory in bash, but I find myself reaching for PS more and more. The problem is that you really need an interface for loading software components into your system at runtime, which .NET provides, but aside from .NET or COM I am unaware of any other equivalent system. Java's OSGi is the closest, and ugh...
- chubot 6y ago
  I haven't used PowerShell much, but I skimmed a 500+ page book on it, and I've heard a lot of mixed feedback on it. Some people love it and some people hate it. Some more responses here: https://news.ycombinator.com/item?id=24873410 https://news.ycombinator.com/item?id=24873410 I guess what I'll say is that I hope the Oil ecosystem will grow the things that people like about it, that aren't tied to Windows. Windows and Unix are fundamentally different and it means they need fundamentally different shells, since a shell is by definition a language closely tied to the OS. You can run powershell on Unix, and bash on Windows, but even on the same OS they are somewhat disjoint tools!

by chubot 6y ago

madhadron 6y ago

So I recently started a job where I'm on Windows, and I've found myself surprisingly enamored of PowerShell. So many of the things that the shell got wrong are done right. The authors wanted to use <, >, etc. as their real meanings, but apparently the early users rebelled at the idea that > was no longer redirect to file. But things that would be nightmares in unix shells, such as going in and adding a new element as the last child of only one of four elements in an XML document (based on its attribute value) are a few lines of code. I still have decades of muscle memory in bash, but I find myself reaching for PS more and more. The problem is that you really need an interface for loading software components into your system at runtime, which .NET provides, but aside from .NET or COM I am unaware of any other equivalent system. Java's OSGi is the closest, and ugh...

chubot 6y ago
I haven't used PowerShell much, but I skimmed a 500+ page book on it, and I've heard a lot of mixed feedback on it. Some people love it and some people hate it. Some more responses here: https://news.ycombinator.com/item?id=24873410 https://news.ycombinator.com/item?id=24873410 I guess what I'll say is that I hope the Oil ecosystem will grow the things that people like about it, that aren't tied to Windows. Windows and Unix are fundamentally different and it means they need fundamentally different shells, since a shell is by definition a language closely tied to the OS. You can run powershell on Unix, and bash on Windows, but even on the same OS they are somewhat disjoint tools!