PowerShell is now opensource

[iamjsed]

This is Microsoft returning the favor for getting bash

 

https://azure.microsoft.com/en-us/blog/powershell-is-open-sourced-and-is-available-on-linux/

[Northstorm]

Nooooice!

[AresKrieger]

Huh interesting

 

 

_{Now make windows 7 open source :p.}

[iamjsed]

I just hope they opensource DirectX haha

 

[LAwLz]

My first few thoughts without reading though anything.

 

 

1) Why would anyone use PowerShell over bash on GNU/Linux?

 

2) How will this actually work? As far as I know, scripting in PowerShell uses a fuckton of objects. That will be clunky and awkward to use on GNU/Linux which uses files and text. I got a feeling that using PowerShell on GNU/Linux will be like trying to screw in a screw with a hammer.

 

3) In before this is "Embrace, extend and extinguish". For those who don't know, it is a tactic Microsoft came up with to kill competitors which are ahead of them. Here are the three steps:

Quote

1) Embrace: Development of software substantially compatible with a competing product, or implementing a public standard.
 

2) Extend: Addition and promotion of features not supported by the competing product or part of the standard, creating interoperability problems for customers who try to use the 'simple' standard.
 

3) Extinguish: When extensions become a de facto standard because of their dominant market share, they marginalize competitors that do not or cannot support the new extensions.

A few examples of Microsoft using this tactic can be found on Wikipedia.

 

4) 100% PR move. Wake me up when they open source something actually important, like the Win32 APIs, the NT kernel, Direct X or something along those lines. You know, the things that are actually locking people to Windows. Not some crappy shell that nobody uses.

[KuJoe]

So now do I convert my Powershell scripts to bash or my bash scripts to Powershell? I never thought I'd have to think about this question.

[Nowak]

48 minutes ago, LAwLz said:

1) Why would anyone use PowerShell over bash on GNU/Linux?

Remote Windows administration when a Linux machine is more easily accessible to you. PowerShell is a very powerful tool for local and remote Windows administration.

[2FA]

1 hour ago, LAwLz said:

My first few thoughts without reading though anything.

 

 

1) Why would anyone use PowerShell over bash on GNU/Linux?

 

2) How will this actually work? As far as I know, scripting in PowerShell uses a fuckton of objects. That will be clunky and awkward to use on GNU/Linux which uses files and text. I got a feeling that using PowerShell on GNU/Linux will be like trying to screw in a screw with a hammer.

 

3) In before this is "Embrace, extend and extinguish". For those who don't know, it is a tactic Microsoft came up with to kill competitors which are ahead of them. Here are the three steps:

A few examples of Microsoft using this tactic can be found on Wikipedia.

 

4) 100% PR move. Wake me up when they open source something actually important, like the Win32 APIs, the NT kernel, Direct X or something along those lines. You know, the things that are actually locking people to Windows. Not some crappy shell that nobody uses.

Being able to use the same shell on every machine allows you to automate your environment easier and faster than you normally would. I'm also expecting full Linux support in Active Directory to follow based off of Microsoft's recent actions. 

 

TL;DR Enterprise use, not consumer use.

[LAwLz]

2 minutes ago, DeadEyePsycho said:

Being able to use the same shell on every machine allows you to automate your environment easier and faster than you normally would. I'm also expecting full Linux support in Active Directory to follow based off of Microsoft's recent actions. 

 

TL;DR Enterprise use, not consumer use.

I am 99% sure you can already push out PowerShell scripts to run in client computers in your Windows domain, so it wouldn't help with that.

 

If you by "automate your environment easier and faster" mean deploying the same script on both GNU/Linux and Windows machines in your network then that will probably not happen either. You will most likely have to use separate scripts for GNU/Linux and Windows since they are so widely different.

[deviant88]

open source windows or gtfo

[2FA]

Just now, LAwLz said:

I am 99% sure you can already push out PowerShell scripts to run in client computers in your Windows domain, so it wouldn't help with that.

 

If you by "automate your environment easier and faster" mean deploying the same script on both GNU/Linux and Windows machines in your network then that will probably not happen either. You will most likely have to use separate scripts for GNU/Linux and Windows since they are so widely different.

You missed the point by a mile. Being able to fully admin both OSes in AD would be a god send for Network Admins everywhere.

 

You will likely be able to run scripts on both Linux and Windows machines without much tweaking. Partly the reason they brought BASH to Windows.

 

[LAwLz]

23 minutes ago, DeadEyePsycho said:

You missed the point by a mile. Being able to fully admin both OSes in AD would be a god send for Network Admins everywhere.

PowerShell on GNU/Linux won't allow you to do this.

It's not PowerShell that makes Windows clients hook into AD so well. It's GPOs and other Windows-specific things which allows for that.

 

AD has very little to do with PowerShell in general.

 

 

23 minutes ago, DeadEyePsycho said:

You will likely be able to run scripts on both Linux and Windows machines without much tweaking. Partly the reason they brought BASH to Windows.

Ehm no.

1) Depending on what you want to do, it might require very little tweaking or a metric ton of tweaking (if it is possible at all). System settings and configuration will still not be cross-compatible because Windows and GNU/Linux are completely different in that regard.

2) According to Microsoft themselves, the reason why they brought bash to Windows was because developers (mainly web developers) asked for it, so that they did not have to change to different developer tools when working on Windows. I have never seen them mention bringing bash to Windows for management reasons.

[Linus_torvalds]

Who needs powershell lol. I use bash on my linux machine, on mac too and on my mobile too (Sailfish OS) even on my router (OpenWRT )

 

MS if you are good guy and you love linux opensource DirectX.

[GoodBytes]

This news post does not meet the posting guidelines:

Moved to Operating System > Windows

[2FA]

32 minutes ago, LAwLz said:

PowerShell on GNU/Linux won't allow you to do this.

It's not PowerShell that makes Windows clients hook into AD so well. It's GPOs and other Windows-specific things which allows for that.

 

AD has very little to do with PowerShell in general.

 

 

Ehm no.

1) Depending on what you want to do, it might require very little tweaking or a metric ton of tweaking (if it is possible at all). System settings and configuration will still not be cross-compatible because Windows and GNU/Linux are completely different in that regard.

2) According to Microsoft themselves, the reason why they brought bash to Windows was because developers (mainly web developers) asked for it, so that they did not have to change to different developer tools when working on Windows. I have never seen them mention bringing bash to Windows for management reasons.

I'm a Network Admin, I work with AD every day so I know how it works. I didn't say anything about PowerShell scripts in AD, you did. I said that I expect Microsoft to add full Linux support in AD. I mentioned BASH because it does allow for management. I know they are advertising it for developers but that doesn't mean it doesn't have other uses. Kind of like how you don't need Cygwin anymore to make use of Rsync backups over SSH.

[LAwLz]

59 minutes ago, DeadEyePsycho said:

I'm a Network Admin, I work with AD every day so I know how it works. I didn't say anything about PowerShell scripts in AD, you did. I said that I expect Microsoft to add full Linux support in AD. I mentioned BASH because it does allow for management. I know they are advertising it for developers but that doesn't mean it doesn't have other uses. Kind of like how you don't need Cygwin anymore to make use of Rsync backups over SSH.

If you're not talking about scripting in AD, why did you bring up AD at all? If you aren't talking about that then AD is completely unrelated to PowerShell.

 

I really don't understand your post in that case. Why did you reply to me? Which part of my post were you responding to ?

If you go back and read the posts again, you will see that I am always talking about PowerShell (which this whole topic is about). I was not talking about integrating GNU/Linux machines into AD (which seems to be what you're talking about, for some reason).

[2FA]

4 hours ago, LAwLz said:

If you're not talking about scripting in AD, why did you bring up AD at all? If you aren't talking about that then AD is completely unrelated to PowerShell.

 

I really don't understand your post in that case. Why did you reply to me? Which part of my post were you responding to ?

If you go back and read the posts again, you will see that I am always talking about PowerShell (which this whole topic is about). I was not talking about integrating GNU/Linux machines into AD (which seems to be what you're talking about, for some reason).

I replied because you were saying that having the same shell doesn't do much.

 

My second part was just saying that I could see MS integrating Linux into AD considering all of things they have already done with Linux such as their own distro, .NET, PowerShell, BASH. Wasn't directly at you, just in general.

[LAwLz]

5 hours ago, DeadEyePsycho said:

I replied because you were saying that having the same shell doesn't do much.

 

My second part was just saying that I could see MS integrating Linux into AD considering all of things they have already done with Linux such as their own distro, .NET, PowerShell, BASH. Wasn't directly at you, just in general.

Well that's not exactly what I but yes, I still don't see why anyone would use PowerShell over bash on GNU/Linux. 

You won't be able to run the same setup scripts on both platforms since they are so widely different. You might be able to do some basic stuff that doesn't touch the OS but that's about it.