PowerShell is open sourced and is available on Linux

Post by jimmaswell » Thu, Aug 18, 2016, 6:09 PM UTC

artimaeis wrote: post #287

jimmaswell wrote: post #278

Earlier quoted context omitted.

In what way was C#'s tooling not better?

Java seemed to have a lot more options for deployments and monitoring for a long time. More advanced 3rd party libraries in general. It had simply been around longer and thus had those tools available. Now that C# has been standard for a while almost all of those tools have a C# equivalent. As a .NET dev I'd actually argue that the things available to C# now are actually better (especially Visual Studio), but that's…

Post by larrik » Thu, Aug 18, 2016, 6:10 PM UTC

larrik wrote: post #230

ldiracdelta wrote: post #94

Earlier quoted context omitted.

If you put this in your `~/.inputrc` [1]: "\e[A": history-search-backward "\e[B": history-search-forward "\e[C": forward-char "\e[D": backward-char you can start typing a previous command and go up through your history for all commands starting with whatever you currently have typed into the bash shell. Reset the scrolling through the history with `ctrl+c`. Personally, I hate that powershell remembers your position i…

I think I tried something like this once before, and it broke something else. I can't remember what that was, so I'm totally trying this.

Post by ianai » Thu, Aug 18, 2016, 6:11 PM UTC

vmarsy wrote: post #79

Great! So I can now run bash on windows (with WSL), open tmux, and open powershell prompts in each tab: the loop is complete! I wish powershell's documentation was a bit more clear about what's powershell 1.0, 2.0, 3.0... Etc. A lot of time I'd find a verbose and tedious way to do one thing because the code was written in "old powershell", when the latest version had a much more elegant solution (either because of ne…

Post by ygra » Thu, Aug 18, 2016, 6:11 PM UTC

emodendroket wrote: post #190

new_hackers wrote: post #166

Earlier quoted context omitted.

ArrayList.Add ... whatever ... | Out-Null Its not implicitly returning. The return value wasn't assigned so it is emitted to the pipeline.

OK, sorry (there is an explicit "return" keyword that I thought worked the same way). Either way, yes, I know you can avoid it by piping to Out-Null, but that behavior is surprising.

    return {expression}

    {expression}
    return

    $array = @()
    $array += $item

Post by mbrumlow » Thu, Aug 18, 2016, 6:12 PM UTC

haberman wrote: post #293

astrodust wrote: post #149

Earlier quoted context omitted.

This is why I find PowerShell to be an answer to a question nobody asked. If bash/zsh isn't cutting it for you, drop into something like Python, Ruby or Perl to do the heavy lifting. PowerShell will never accumulate a library as comprehensive as what any of those three have, each has had decades to accumulate packages of all kinds, and more are still being added. It's odd, but not surprising given their history of "N…

> This is why I find PowerShell to be an answer to a question nobody asked. If bash/zsh isn't cutting it for you, drop into something like Python, Ruby or Perl to do the heavy lifting. How are Python/Ruby/Perl going to give you structured objects from "ps"? That's the promise of object-based pipes. You can get useful records out of your command-line tools without having to write an ad-hoc regex.