4 ms·

I strongly recommend against learning Powershell, it has horrid syntax and is not crossplatform. It wants to be a pseudo C# but without being C#. And anyway yo

by knocte 10y ago

I strongly recommend against learning Powershell, it has horrid syntax and is not crossplatform. It wants to be a pseudo C# but without being C#. And anyway you can use scriptcs nowadays to write scripts in C# (or even better: .fsx scripts, with F#, which is more succint, less verbose than C#).

majkinetor 10y ago
You should really really inform yourself better.
jodrellblank 10y ago
I strongly recommend against believing people who say PS is not cross platform when it is available for macOS and Linux and is open source too.
- robert_tweed 10y ago
  Interesting. Does it actually work though, or does it tend to depend on Windows-specific assemblies to do any useful work? The main use-case I have for Powershell is remotely administering Exchange. If I could do that from OSX or Linux, then that would be useful enough for me to spend the time learning it.
  - Arnavion 10y ago
    It's based on .Net Core, so anything not in core PS has to be available there.
  - NetStrikeForce 10y ago
    > The main use-case I have for Powershell is remotely administering Exchange. If I could do that from OSX or Linux, then that would be useful enough for me to spend the time learning it. I guess you can always do powershell remoting? Apparently it also works from Windows to Linux! https://github.com/PowerShell/PowerShell/blob/866b558771a20cca3daa47f300e830b31a24ee95/docs/new-features/remoting-over-ssh/README.md https://github.com/PowerShell/PowerShell/blob/866b558771a20c... (got pointed there from this Reddit post: https://www.reddit.com/r/PowerShell/comments/4ziw85/anyone_manage_to_get_enterpssession_or/ https://www.reddit.com/r/PowerShell/comments/4ziw85/anyone_m... )
intrasight 10y ago
I agree. If you like C# better (who wouldn't), then you should at least play around a bit with C# Scripting. A good starter article: https://msdn.microsoft.com/en-us/magazine/mt614271.aspx https://msdn.microsoft.com/en-us/magazine/mt614271.aspx
deleted 10y ago
[deleted]
YeGoblynQueenne 10y ago
>> It wants to be a pseudo C# but without being C#. Where did that come from? You can instantiate .Net classes from the command line in powershell, but otherwise it's got nothing to do with C#. Pretty much the only relation between psh and C# that I can think of is that they are two of the three least un-microsofty pieces of software from Microsoft, and they're both really nice to use (the third one being Visual Studio). Other than that, they don't really have anything in common.
mondoshawan 10y ago
> Horrid syntax True enough, but I'd rather make use of all of the tools I have available on as many platforms as I have available to me so that I don't have to fight to do things with limited tools. GUI is nice, but knowing how the underlying system integrates together through a shell is infinitely better. > Not crossplatform Didn't they port to Linux and Mac?
- Aloha 10y ago
  I only suggest that the people who named certain commands must type 500 wpm. Shit can be really really long.
  - ygra 10y ago
    That's what tab completion and aliases are for. The long command names are mainly there so that everything is consistent and there's not much guessing involved what a command does (or when you need to find something).

by knocte 10y ago

majkinetor 10y ago

You should really really inform yourself better.

jodrellblank 10y ago

I strongly recommend against believing people who say PS is not cross platform when it is available for macOS and Linux and is open source too.

robert_tweed 10y ago
Interesting. Does it actually work though, or does it tend to depend on Windows-specific assemblies to do any useful work? The main use-case I have for Powershell is remotely administering Exchange. If I could do that from OSX or Linux, then that would be useful enough for me to spend the time learning it.
- Arnavion 10y ago
  It's based on .Net Core, so anything not in core PS has to be available there.
- NetStrikeForce 10y ago
  > The main use-case I have for Powershell is remotely administering Exchange. If I could do that from OSX or Linux, then that would be useful enough for me to spend the time learning it. I guess you can always do powershell remoting? Apparently it also works from Windows to Linux! https://github.com/PowerShell/PowerShell/blob/866b558771a20cca3daa47f300e830b31a24ee95/docs/new-features/remoting-over-ssh/README.md https://github.com/PowerShell/PowerShell/blob/866b558771a20c... (got pointed there from this Reddit post: https://www.reddit.com/r/PowerShell/comments/4ziw85/anyone_manage_to_get_enterpssession_or/ https://www.reddit.com/r/PowerShell/comments/4ziw85/anyone_m... )

intrasight 10y ago

I agree. If you like C# better (who wouldn't), then you should at least play around a bit with C# Scripting. A good starter article: https://msdn.microsoft.com/en-us/magazine/mt614271.aspx https://msdn.microsoft.com/en-us/magazine/mt614271.aspx

deleted 10y ago

[deleted]

YeGoblynQueenne 10y ago

>> It wants to be a pseudo C# but without being C#. Where did that come from? You can instantiate .Net classes from the command line in powershell, but otherwise it's got nothing to do with C#. Pretty much the only relation between psh and C# that I can think of is that they are two of the three least un-microsofty pieces of software from Microsoft, and they're both really nice to use (the third one being Visual Studio). Other than that, they don't really have anything in common.

mondoshawan 10y ago

> Horrid syntax True enough, but I'd rather make use of all of the tools I have available on as many platforms as I have available to me so that I don't have to fight to do things with limited tools. GUI is nice, but knowing how the underlying system integrates together through a shell is infinitely better. > Not crossplatform Didn't they port to Linux and Mac?

Aloha 10y ago
I only suggest that the people who named certain commands must type 500 wpm. Shit can be really really long.
- ygra 10y ago
  That's what tab completion and aliases are for. The long command names are mainly there so that everything is consistent and there's not much guessing involved what a command does (or when you need to find something).