4 ms·

This looks kind of like Powershell, which I've been in awe of for several months now. But being built on a more dynamic runtime this will have the ability to us

by dant 18y ago

This looks kind of like Powershell, which I've been in awe of for several months now. But being built on a more dynamic runtime this will have the ability to use to extend objects that you get back from the shell so it could be even better.

zcrar70 18y ago
Powershell is pretty cool, but its syntax takes a little getting used to. I keep wondering why they chose to create a new syntactic paradigm when they are already so many around...
- smhinsey 18y ago
  I agree with this. It's a hugely impressive product, but the syntax is rather off-putting. I also feel that the default settings it installs with aren't too great because you can't run scripts in files without changing the environment -- the security angle makes sense, but it makes what's already a hard sell in the Microsoft world (a new shell) even tougher.
hayeah2 18y ago
ya, i think the significance of rubish (to myself anyway) isn't so much interactivity (it's plausible, but not convincing), but this potential to abstract my personal usage pattern in Ruby. abstraction is a form of memory.
- jballanc 18y ago
  First: Thanks! I've been meaning to do exactly this once I had even a spare moment (consider yourself forked! ;-)... Second: I think where this will really shine is in the "twilight zone" of shell scripting. So often, I start off with a short chain of commands on the command prompt. I'll keep adding to the chain, until at some point I feel the need to move this elaborate chain (usually an alias at that point) into it's own script file. I could copy directly, but then any improvements would require continuing to use shell script (ugh). On the other hand, I could translate the existing script to Ruby, but then I'd have to put in the overhead to do the translation with no immediate gain. With this, I could see doing a direct copy-->paste from command line to script file and just keep going...or better yet, since it's all Ruby, why not an extension on File to automatically write out X lines of history to a script file? ...oooooh! I'm excited already!

by dant 18y ago

zcrar70 18y ago

Powershell is pretty cool, but its syntax takes a little getting used to. I keep wondering why they chose to create a new syntactic paradigm when they are already so many around...

smhinsey 18y ago
I agree with this. It's a hugely impressive product, but the syntax is rather off-putting. I also feel that the default settings it installs with aren't too great because you can't run scripts in files without changing the environment -- the security angle makes sense, but it makes what's already a hard sell in the Microsoft world (a new shell) even tougher.

hayeah2 18y ago

ya, i think the significance of rubish (to myself anyway) isn't so much interactivity (it's plausible, but not convincing), but this potential to abstract my personal usage pattern in Ruby. abstraction is a form of memory.

jballanc 18y ago
First: Thanks! I've been meaning to do exactly this once I had even a spare moment (consider yourself forked! ;-)... Second: I think where this will really shine is in the "twilight zone" of shell scripting. So often, I start off with a short chain of commands on the command prompt. I'll keep adding to the chain, until at some point I feel the need to move this elaborate chain (usually an alias at that point) into it's own script file. I could copy directly, but then any improvements would require continuing to use shell script (ugh). On the other hand, I could translate the existing script to Ruby, but then I'd have to put in the overhead to do the translation with no immediate gain. With this, I could see doing a direct copy-->paste from command line to script file and just keep going...or better yet, since it's all Ruby, why not an extension on File to automatically write out X lines of history to a script file? ...oooooh! I'm excited already!