|
OriginalGriff wrote: Either that or it spells a lot of extra (hopefully chargeable) support work come our way when the users hear about it ...
Yeah - as soon as users try to do something that deviates from the simplest scenarios. Then you're back to writing a real app.
|
|
|
|
|
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
Power Automate is part of their low code/no code platform. I have looked at it but have not done much with it yet.
|
|
|
|
|
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
|
|
|
|
|
A plague, yes.
The only time I had to dabble with PowerShell (ptui) it was because a colleague had sent me a small script to run to demonstrate something. I quickly took the ideas and wrote a proper C# program to do it better/quicker/etc. In that way, it may be that the PowerShell (ptui) script was just enough to pass along the necessary information I needed.
Lately, I've begun to wonder whether or not PowerShell (ptui) and Python (ptui ptui) serve the same role. Both seem to be glue languages with little they can do natively, but the user is expected to import functionality written in proper programming languages.
|
|
|
|
|
much like VB of old (and perhaps where VB should have stayed)
Real programmers use butterflies
|
|
|
|
|
It is simple compared to bash. See bash if: naked, parentheses, double parentheses, brackets, double brackets. Exporting variables, and using those in parent shells. bash is a tad more logical than cmd.exe is, but no match for powershell. Just try to use your date handling routines NOT in your locale.
|
|
|
|
|
How come I had no trouble learning Bash then? and PS? No. I cannot remember the syntax at all.
Real programmers use butterflies
|
|
|
|
|
Maybe because the basic syntax is quite similar (except the parentheses magic), and many command has bash-alias? So it was powershell looking as bash? 
|
|
|
|
|
If the syntax was similar I'd have had no problem learning Powershell. Bash and Powershell syntax are quite different.
Real programmers use butterflies
|
|
|
|
|
As a REPL, I dislike its verbosity but for writing scripts it's fantastic compared to bash, so much simpler.
Spacing around `=` is irrelevant instead of throwing weird errors.
The if statement behaves like a programming language and does not have weird stuff like [[ ]] that changes something..
I never understood bash as a language.
That being said, I miss quite some stuff from coreutils on windows.. and I just realized that Git installs them and just added `C:\Program Files\Git\usr\bin` to the path, so I don't actually miss them anymore
|
|
|
|
|
I feel the exact opposite of you. I cannot remember PS syntax. It confounds me. Bash is no trouble.
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: 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?
To be honest, if your camera knows it's a cat, then it's confused already, and probably need AIchiatric help ...
"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!
|
|
|
|
|
you know what I meant! 
Real programmers use butterflies
|
|
|
|
|
I did try to like PS but failed, I also use bash for my Linux scripts and whilst they can be challenging I much prefer them to PS.
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
I spent a few years managing Exchange (2012ish) and the GUI would produce, and show, the PS commands. Of course I memorized them all.
Your camera shows that for the same reason my VHS recorder still blinks 12:00.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
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.
|
|
|
|
|
Because > is used for I/O redirection. < > | are at least consistent across most script languages
|
|
|
|
|
Yeah, I like it. I'm an old timer - lots of bash. Once I finally got used to the idea that powershell wasn't bash I started to like it. (I made some hilarious mistakes on the way) Now sometimes in bash I find myself wishing for objects.
|
|
|
|
|
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
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
