5 ms·
It seems odd that any paper on this topic (I read both TFA and the paper it references) would not mention PowerShell once, nor the broader issue of how the Unix
by PaulDavisThe1st 5y ago
It seems odd that any paper on this topic (I read both TFA and the paper it references) would not mention PowerShell once, nor the broader issue of how the Unix shell uses text streams as the only intermediary format between pipeline components.
- adamnemecek 5y agounix people like is a solipsistic world where windows doesn’t exist.
- mmcgaha 5y agoNope, unix people like the fact that thirty-year-old shell scripts still work just fine. In ten years, powershell will be be replaced and it will be the new vbscript. No thanks.
- jeppesen-io 5y agoTo have a real discussion on the future of shells while ignoring the PowerShell is not an honest discussion. I'm not sure why you'd want to run a 30 year old script when the computing environment has changed so much around those scripts. Regardless of what future you see for PowerShell as a product, the concepts and implementation, is a great place to see what works well and what didn't, particularly when it comes to non-text oriented pipeing
- cybernautique 5y agoStability is an important thing. The fact that 30 year old scripts still work, and still can be run, is a testament to the staying power of the underlying technology. That staying power generally means some reduction in cognitive load: I can use the same semantics, principles, and idioms on my phone, laptop, and computer. That's good. That's powerful. Contrast that with the JavaScript framework du jour: React today, React with new shiny hooks tomorrow; Svelte a week ago and a week from now; while the boss just told you in an email that the meeting an hour from now regards porting everything to Vue. That's the kind of cognitive load that we're thankfully spared by long-lasting technology. Now consider PowerShell. It is not an open standard. It is not an open technology. Its steward is Microsoft, of "Embrace, Extend, Extinguish" fame. It bucks against the long-established norm, so that all the established idioms are useless, while its semantics are just as tedious. Why, therefore, should I bother putting pilot time into this proprietary flying rug whose engine is more-likely-than-not a cracked bottle of Microsoft semen? As to whether PowerShell has anything to teach us about shell engineering: meh. It's not as good as Bash at doing Bash-like things and it's not as good as scripting languages at doing scripting things. EDIT: I figured I'd look to see whether PowerShell is open. Surprisingly, it is! With an MIT license to boot. However, as expected with any Microscum code, it includes telemetry out-of-the-box. As a matter of principle: I don't like it, I don't trust it, I don't want it. The semantics are ugly and it stinks of Microsoft.
- zerocount 5y agoI always thought PowerShell was slow and it's got the whole .net baggage with it. Good one with the "Microsoft semen!" Had me laughing out loud.
- hutzlibu 5y agoI think a fairer comparison would be comparing bash to vanilla js. Old vanilla js works the same today, as it did in the beginning. And react would be your systemD/wayland, whatever. Environments change, thats allright. And I think it is not smart to not look out for good ideas, even if they come from microsoft. What changed are the surroundings (and enhancements).
- deleted 5y ago[deleted]
- cachvico 5y agoIn 10 years, unix scripts will work fine, Powershell scripts will work fine, and veterans of both sides will still be arguing about which to use.
- TrumpRapedWomen 5y agoPowerShell is a vast improvement over every Linux/Unix shell I have every used.
- ReleaseCandidat 5y ago> Nope, unix people like the fact that thirty-year-old shell scripts still work just fine. No, they don't. Because even if a Unix from 30 years ago still does exist (Solaris and Aix) it and the programs used with it changed that much that almost all scripts are unusable by now. And the used shells (Korn shell anyone?) and the shells themselves changed too. Same with Linux, it changed that much during the last 10 years, that almost any script had to be rewritten.
- kaba0 5y ago> the fact that thirty-year-old shell scripts still work just fine With 30 years old bugs because bash can’t be written correctly. I really don’t understand why are we putting up with that — anything longer than #! line and one command invocation in bash should be a python script instead.
- IshKebab 5y agoHa yeah right. 0 year old shell scripts barely work.
- cybernautique 5y agoI specifically and purposefully ignore anything Microsoft. I'm interested in open computing, which Windows and Microsoft exist to spite. I assume Microsoft does everything in bad faith, and that any technology they deploy is ultimately in service of their walled gardens. I refuse to participate; I won't let myself be walled-in, and I won't give them any credibility. Windows does exist, but it ought not to.
- zerocount 5y agoAnd it keeps getting worse with each version.
- TrumpRapedWomen 5y agoYou really need to update your attitude, the new Microsoft has embraced open source in a very real and meaningful way. https://dotnet.microsoft.com/en-us/download https://dotnet.microsoft.com/en-us/download https://github.com/PowerShell/PowerShell https://github.com/PowerShell/PowerShell PowerShell is SO much better than any Linux/Unix shell.
- agumonkey 5y agoI think it will change. I sense a reactive trend that will impact sys/shell interactions coming.
- d0mine 5y agoPowerShell might not satisfy: "Universal composition, Stream processing, Unix-native" points. Have you tried to pipe some bytes via PowerShell? Binary pipeline looks complicated https://stackoverflow.com/questions/33936074/decode-powershell-output-possibly-containing-non-ascii-unicode-characters-into-a https://stackoverflow.com/questions/33936074/decode-powershe...
- jeppesen-io 5y agoI'd suspect the OP would not say PowerShell is perfect or should be the *nix future, but that it's worth evaluating the ideas it brings to the table 50 years is quite the time horizon after all
- jeppesen-io 5y agoAs someone who moved to Linux full-time, professionally and personally, there are times I do miss PowerShell. Never used anything like it. To tab complete "apis" and complex data structures was very enjoyable For better or worse, it's what I and my team used to manage a decent size VMware cluster of a hundred hosts and 6k VMs ( I think, it was a very long time ago) Wouldn't go back, but there are aspects I miss
- cobalt 5y agopowershell (core) is on linux btw
- hnlmorg 5y agoPowershell is available on Linux. Albeit it doesn't always play too nicely with existing CLI tools. There are also other typed shells that appeal to yourself which aren't Powershell but do have behaviours similar to Powershell and which do play a lot more nicely with the wider Linux / UNIX ecosystem: - murex https://github.com/lmorg/murex https://github.com/lmorg/murex - Elvish https://github.com/elves/elvish https://github.com/elves/elvish - NGS https://github.com/ngs-lang/ngs https://github.com/ngs-lang/ngs I'm the maintainer of murex so happy to answer any questions on that shell here. I do know the the maintainers of Elvish and NGS pop on HN too.
- hulitu 5y agoIt seems odd that everytime there is a discussions about shells on UNIX, an ad to powershell comes in. Powershell might have its virtues but: 1)One cannot rely on it for system administration when limited resources are available. 2) even on windows is slow to start. 3) documentation is ... where ?
- jasode 5y ago>everytime there is a discussions about shells on UNIX, an ad to powershell comes in. The gp (Paul) is not "advertising Powershell" and he's not recommending people switch to it. Instead, he's saying that it's strange that an academic paper talking about future concepts doesn't even have a cursory survey of what other popular shells have done. Here's an example of that style of writing where other platform technologies are mentioned: Joshua Bloch is a ex-Sun employee and Java advocate proposing new syntax for Automatic Resource Management and in his note, he mentions what C# and C++ did: http://mail.openjdk.java.net/pipermail/coin-dev/2009-February/000011.html http://mail.openjdk.java.net/pipermail/coin-dev/2009-Februar... It shouldn't have to be said that citing C# & C++ does not mean it's an "ad for C#". When a new 2021 paper about future of shells has no mention of zsh, Powershell, etc by the authors, it's reasonable for readers to wonder if the team has overlooked what others have done. E.g. Powershell was designed by ex-UNIX admins.