Microsoft Open sources Powershell, Brings it to Mac and Linux
32 replies, posted
[url]http://www.zdnet.com/article/microsoft-open-sources-powershell-brings-it-to-linux-and-mac-os-x/[/url]
[QUOTE]As recently rumored, Microsoft is open sourcing PowerShell and making a version of the tool available for Linux and Mac OS X.
As of today, August 18, Microsoft is making available alpha releases of PowerShell Core on Linux (Red Hat, Ubuntu and CentOS) and Mac OS X on GitHub as a binary release. More platforms will be available in the future, company officials said. Microsoft also will be releasing the source code for both the Windows and Linux versions of PowerShell today.
Because PowerShell is .NET-based, Microsoft needed .NET on other platforms in order to bring PowerShell to other platforms, said Microsoft Technical Fellow and father of PowerShell Jeffrey Snover.[/QUOTE]
Oh good, a shell for when zsh won't fulfill your masochistic desires!
I mean I like powershell a lot, and I mean a lot, because I use it daily and for automating tons of things. Because fuck batch and VBScript.
But that's also it as well. It was designed with the object oriented ness of Windows in mind. How would it be useful on systems like OS X and Linux? Beyond PS Remoting of course.
Still not as good as bash tbh, unless it's for cross platform build scripts or something - though I can't see them putting Visual Studio second to anything
[QUOTE=Luni;50914346]Still not as good as bash tbh[/QUOTE]
It might be good for people who have to deal with Linux and OS X PCs every once in awhile but are vastly more proficient with powershell than bash. Each shell has some pretty advanced features you can learn to make use of, so even if it's a little awkward to use powershell in a Unix environment, it might still be worth it.
Kind of like how a lot of Linux users will use bash on windows with mingw or cygwin, despite it being a bit awkward and there being a perfectly fine powershell installed by default.
microsoft is really bipolar lately, with doing great things like this then proceeding to mess up windows 10 with forced updates and stuff
[QUOTE=Demache;50914232]I mean I like powershell a lot, and I mean a lot, because I use it daily and for automating tons of things. Because fuck batch and VBScript.
But that's also it as well. It was designed with the object oriented ness of Windows in mind. How would it be useful on systems like OS X and Linux? Beyond PS Remoting of course.[/QUOTE]
It can load and interface with CLR assemblies, but that's about it I think.
[QUOTE=thelurker1234;50912266]Oh good, a shell for when zsh won't fulfill your masochistic desires![/QUOTE]
... What's wrong with zsh? I've been using it for ages with no problems. It's just a mildly better shell, with an active ecosystem around it.
[QUOTE=nikomo;50920346]... What's wrong with zsh? I've been using it for ages with no problems. It's just a mildly better shell, with an active ecosystem around it.[/QUOTE]
Yeah zsh is cool, just a better bash.
[t]https://i.imgur.com/FhjdXZo.png[/t]
does powershell take several seconds to start for anyone else? What is that shit? urxvt takes literally < 1second to open on linux
I tried a "Python as a shell" project at one point, and it took a good 10 seconds to open. That was even more hilarious than how slow Powershell is.
[QUOTE=nikomo;50920367]I tried a "Python as a shell" project at one point, and it took a good 10 seconds to open. That was even more hilarious than how slow Powershell is.[/QUOTE]
I'm a python fanboy myself, but I must vomit at the thought of using python as a shell... it's just utterly wrong
Bash is my favorite so on windows I just use Babun. It's got p much every linux utility built in (plus technically a package manager!!!). Can't see myself ever moving to powershell once getting used to bash, only the other way around.
[QUOTE=proboardslol;50920359]does powershell take several seconds to start for anyone else? What is that shit? urxvt takes literally < 1second to open on linux[/QUOTE]
It has to initialize the entire .NET library and import all the default cmdlets for autocomplete, syntax highlighting etc. Everything powershell does is through scripts and .NET. Remember, its not text based like bash, its object oriented so there is a lot more overhead. You can't treat it like a *NIX shell because it isn't one. Its meant for Windows management. In fact, if you want to do anything remotely advanced in a Windows enterprise environment, you have to use Powershell.
It also launches instantly once you have launched it once as its cached so its not a big deal.
[QUOTE=eirexe;50920354]Yeah zsh is cool, just a better bash.
[t]https://i.imgur.com/FhjdXZo.png[/t][/QUOTE]
is that zsh, or is that just the application you're using to run a zsh shell?
[QUOTE=nikomo;50920346]... What's wrong with zsh? I've been using it for ages with no problems. It's just a mildly better shell, with an active ecosystem around it.[/QUOTE]
Just a little joke about some of the people that use it. It's good if you need the features.
In case anyone hasn't seen it
check out the drama
[url]https://github.com/PowerShell/PowerShell/pull/1901[/url]
[QUOTE=runtime;50920793]is that zsh, or is that just the application you're using to run a zsh shell?[/QUOTE]
my terminal emulator is Guake which is a dropdown quake style terminal, my theme is agnoster
[editline]20th August 2016[/editline]
[QUOTE=Scratch.;50920903]In case anyone hasn't seen it
check out the drama
[url]https://github.com/PowerShell/PowerShell/pull/1901[/url][/QUOTE]
I don't see how that's drama, if you replace a program without changing the name it should do exactly the same, MS's replacement does not.
[QUOTE=eirexe;50920962]my terminal emulator is Guake which is a dropdown quake style terminal, my theme is agnoster
[editline]20th August 2016[/editline]
I don't see how that's drama, if you replace a program without changing the name it should do exactly the same, MS's replacement does not.[/QUOTE]
i
That's the crux of that whole issue. Those aren't programs, they are aliases for Invoke-WebRequest. And have been there for years. Removing them could break scripts that use those aliases (although they aren't supposed to be used in scripts in the first place).
I do get where the "remove" guys are coming from though, as that does tend to break things in Linux. And may have been a bad idea in hindsight.
[QUOTE=Demache;50920995]i
That's the crux of that whole issue. Those aren't programs, they are aliases for Invoke-WebRequest. And have been there for years. Removing them could break scripts that use those aliases (although they aren't supposed to be used in scripts in the first place).
I do get where the "remove" guys are coming from though, as that does tend to break things in Linux. And may have been a bad idea in hindsight.[/QUOTE]
Has anyone said Embrace, Extend, Extinguish, yet?
[QUOTE=proboardslol;50921528]Has anyone said Embrace, Extend, Extinguish, yet?[/QUOTE]
Like 5 times IIRC from a few hours ago. :v:
Although, I don't think that is the case, its just an oversight because it used to be Windows only. It "made sense" to make *NIX aliases of "equivalent" Powershell commands. I guess to make the transition easier I guess? I dunno.
But I would be liar if I didn't say I use 'ls' for Get-ChildItem literally all the time.
[QUOTE=Demache;50922108]Like 5 times IIRC from a few hours ago. :v:
Although, I don't think that is the case, its just an oversight because it used to be Windows only. It "made sense" to make *NIX aliases of "equivalent" Powershell commands. I guess to make the transition easier I guess? I dunno.
But I would be liar if I didn't say I use 'ls' for Get-ChildItem literally all the time.[/QUOTE]
I just have ls.exe
[t]http://jesusfuck.me/di/GAFF/16-08-21-13-35-52-administrator-windows-powershell.png[/t]
among many other executables for *NIX (scp, touch)
[QUOTE=Scratch.;50922280]I just have ls.exe
[t]http://jesusfuck.me/di/GAFF/16-08-21-13-35-52-administrator-windows-powershell.png[/t]
among many other executables for *NIX (scp, touch)[/QUOTE]
Does yours support unicode because ls is impeding on my ability to determine which folder is which here.
[code]>ls -l
total 0
drw-rw-rw- 2 helif 0 0 2016-08-21 14:01 ?????
drw-rw-rw- 2 helif 0 0 2016-08-21 14:05 ?????
>dir
Drive D does not have a label
Volume serial number is 6C39-BCF4
D:\Users\helif\Documents\wow
2016/08/21 14:05 <DIR> .
2016/08/21 14:05 <DIR> ..
2016/08/21 14:01 <DIR> ポルノあり
2016/08/21 14:05 <DIR> ポルノない
0 files 0 bytes
4 directories 1,129,293,258,752 bytes free[/code]
Is it because cygwin is a piece of shit?
[QUOTE=Scratch.;50922280]I just have ls.exe
[t]http://jesusfuck.me/di/GAFF/16-08-21-13-35-52-administrator-windows-powershell.png[/t]
among many other executables for *NIX (scp, touch)[/QUOTE]
The main problem is that NIX commands (or legacy cmd ones for that matter) aren't very useful in powershell beyond automating them. So when your actually interacting with the shell, you want that ability to send the output objects into other cmdlets seamlessly.
[QUOTE=thelurker1234;50912266]Oh good, a shell for when zsh won't fulfill your masochistic desires![/QUOTE]
When you just feel like being in pain, there's powershell for linux.
[QUOTE=Matthew0505;50922508]Why not just make the alias turn off if it detects actual wget or curl usage.[/QUOTE]
Detect usage? How would it do that? You can't use the command in powershell because it already thinks its an alias, and it surely isn't watching your other shell interfaces.
this is one of the many things that can be solved by just adding an option
I've never looked into powershell, but I strongly dislike Bash's syntax for scripts. Is powershell worth learning?
[QUOTE=da space core;50914489]microsoft is really bipolar lately, with doing great things like this then proceeding to mess up windows 10 with forced updates and stuff[/QUOTE]Vast corporations tend to be like that imo; too much going on for management to enforce a puppies and love/sodomise the customer policy across the entire corporation effectively.
[QUOTE=Robber;50922815]I've never looked into powershell, but I strongly dislike Bash's syntax for scripts. Is powershell worth learning?[/QUOTE]
It requires you to learn a bit more about how the scripting system works, and how the .Net platform makes this interaction possible. So there's a bit more to dwelve into before understanding it all, as opposed to a POSIX shell, but it can probably do just about the same tasks I would think.
Sorry, you need to Log In to post a reply to this thread.