4 ms·
Powershell solved all this, Intellisense, introspection, apis for compiled apps (although I think .NET is only), typed output. Still hasn't caught fire though,
by jayd16 6y ago
Powershell solved all this, Intellisense, introspection, apis for compiled apps (although I think .NET is only), typed output.
Still hasn't caught fire though, even for me. I respect it but I still reach for bash. I'm not really sure why except perhaps momentum.
- geocar 6y agoThere are advantages to text. Some of my favourites: 1. Humans can understand text too! 2. Text can travel over every transport. 3. Text is benign. 4. Large text is large and small text is small, but all objects look the same size.
- airstrike 6y agoNot sure how much of this still applies, but I remember reading this a while back when I also realized PS just didn't click for me https://medium.com/@octskyward/the-woes-of-powershell-8737e5346b1 https://medium.com/@octskyward/the-woes-of-powershell-8737e5...
- godtoldmetodoit 6y agoGot about a quarter of the way through and none of it applied to modern Powershell.
- _carbyau_ 6y agoReading that link, even back when it was written it feels like an article of first impressions with the bias of someone comfortable with many hours of use of a Unix shell. 1. Powershell isn't a complete greenfield and exists in a context, which explains many of the complaints. 2. any new tech use requires learning. I could address each point but most galling was the conclusion: "At this point we realise the truth — PowerShell is not designed to be an actual shell for users" Because wget did not output to a file by default?!? Really?!? IMO, this article failed to hit the mark back in 2014 when it was written let alone now. Edit: conciseness
- majkinetor 6y agohttps://news.ycombinator.com/item?id=27055991 https://news.ycombinator.com/item?id=27055991