Power Shell without the complexity? Could be ...
-
whilst a lot of powershell stuff is self explanatory I only really use it via copy and paste as I cannot stand all that typing I have always thought that it was crying out to be implemented using a gui with autocomplete
PowerShell has had tab completion since at least version 2 (2009) which has got better over time. O.K. It's never been as good as Linux/Bash tab completion, but it is there :)
-
Does anyone actually like powershell? I avoid it like the plague. It's confusing, and I say that as someone that mucks about with bash on the regular - not exactly a paragon of syntactic rationality itself. Why can't people make an elephanting simple to use shell? If it needs to be able to do everything, make it "AI" assisted, like one of those old "expert systems" if you have to. Let it learn. And speaking of "AI", why the heck does my camera still name photos like IMG_2021_5_18.jpg or whatever when it knows it's a cat?
Real programmers use butterflies
Personally, I love it. - It doesn't need compiling so I can see where I am going wrong installing (and I go wrong a lot :) ). - Modules are very similar to libraries that you would need to reference in your code in other languages, but work straight from the prompt once installed. - Said modules also allow one-line commands to get the information you need from a variety of different sources/application without writing your own function. Admittedly other scripting languages have a lot of these benefits, oh and I used to be a Windows Sysadmin so I am probably biased :laugh:
-
Does anyone actually like powershell? I avoid it like the plague. It's confusing, and I say that as someone that mucks about with bash on the regular - not exactly a paragon of syntactic rationality itself. Why can't people make an elephanting simple to use shell? If it needs to be able to do everything, make it "AI" assisted, like one of those old "expert systems" if you have to. Let it learn. And speaking of "AI", why the heck does my camera still name photos like IMG_2021_5_18.jpg or whatever when it knows it's a cat?
Real programmers use butterflies
I've grown to like PS. Passing data around in Bash is done purely with plain text strings, which to me means it's as brittle as it can get. PowerShell hangs on to actual objects with properties and methods, and can leverage many things from .NET, so I find working with it is somewhat similar to working with a debugger when I need to explore an object's properties and values as a process is running live. This is particularly valuable when I'm not familiar at all with some new object type. When I want to automate something and building an EXE is overkill, PS is pretty much my go-to solution.
-
Powershell isn't all that bad. At least it is readable by a semi decent normal non PS programmer. Bash. Oh heck if you don't have some actual working knowledge you have no idea what that means. I don't like writing powershell sometimes. But It does seem to work. I hate the -gt -eq signs. What the heck happened to > and = instead. But that is just me, and like all of us. I am weird.
To err is human to really elephant it up you need a computer
-
rnbergren wrote:
hate the -gt -eq signs. What the heck happened to > and = instead
I think this was done deliberately so a PS script could be dropped directly into something like an XML block or HTML with no change.
probably. I still think it is stupid though.
-
Not heard of this before: How to create your first app with the free Windows 10 Power Automate - TechRepublic[^] but it looks kinda interesting. Either that or it spells a lot of extra (hopefully chargeable) support work come our way when the users hear about it ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
I, and a couple of coworkers, installed and tried out the desktop Power Automate. We all came to the same conclusion. That is quite a bit of hassle to do something that Office's build-in macro functions and rules already do better. Money makes the world go round ... but documentation moves the money.
-
Powershell isn't all that bad. At least it is readable by a semi decent normal non PS programmer. Bash. Oh heck if you don't have some actual working knowledge you have no idea what that means. I don't like writing powershell sometimes. But It does seem to work. I hate the -gt -eq signs. What the heck happened to > and = instead. But that is just me, and like all of us. I am weird.
To err is human to really elephant it up you need a computer
-
whilst a lot of powershell stuff is self explanatory I only really use it via copy and paste as I cannot stand all that typing I have always thought that it was crying out to be implemented using a gui with autocomplete
