@HackSlash IKR? Whenever I'm forced to write PowerShell script, I constantly have to do google for every. single. command. and even so, I find that I have mistakes in how I'm passing parameters, etc. etc. etc. so that to produce a 50-line PowerShell script is incredibly slow compared to doing the equivalent in C# or VBA. Heck, I think I'd be more productive in VBScript! It's madness.
and oh why, did they think it was such a great idea to keep running after errors? If my input is garbage, the output will be garbage. Why bother spewing garbage all over the place?!?
I am extremely new to VBA code; however, I have found a resource online that has helped me sync my PivotTable Slicers in Excel. The code seems to work exactly how I want it, but it takes approximately ~9-10 seconds to execute. I was hoping the gurus on here would help me clean up the code and per...
@this PowerShell is the worst offender. They had a chance to go POSIX but they only did a partial implementation, again. Then they decided to bring in the ability to run .NET commands, brilliant! That would be great if PowerShell had functions, which it does but they don't return a value... They return ALL STDOUT? I think whoever made that decision needs to be banished to the realm of the luddites. Never allowed to touch a computer again for his crimes.
I agree. they ended up taking the worst features from each world and mashed it together into one giant tarpit of worst
it's sad because there's so much potential but .... WTH.
doubly frustrating considering that it's an improvement compared to BAT
whether it's an improvement over VBScript is an open question.
I also think their verb-noun model is trash. It's more likely that I have a noun in my mind but I am not sure what verb I need and I end up guessing the verb, failing, and end up having to google the command.... oh, they use THAT verb... what a waste of time it was!
VBA Rubberducking
VBA Rubberducking