r/PowerShell • u/[deleted] • Aug 10 '20
What do you think about PowerShell's future?
What do you think about PowerShell's future? Do you think it's legacy and will be deprecated in the foreseeable future, or do you believe we're in the beginning of PowerShell's golden age? Sometimes I feel like PowerShell is what "low code" or "medium code" should be about. At the same time it's still kind of janky, the language is relatively unknown and it feels like most people don't regard it as particiuarly valuable in the long term.
33
u/CitySeekerTron Aug 10 '20
If you're a windows administrator, it's a requirement. I sincerely hope that it grows and becomes popular in other OS environments. It's unbelievably great.
7
u/ThatsNooseToMe Aug 11 '20 edited Aug 11 '20
I’m the only one on a team of 12 admins that really use it.. blows my mind
26
u/I_ride_ostriches Aug 11 '20
I was sharing Skype management with a guy who was super duper proud of how hard he worked, but knew 0 powershell scripting. Always talking about how late he worked or how long it took him to do stuff like it meant something.
We turned off a feature and he needed to change the policy for all the users that were using that feature, about 1200 worth. He spent a full day at work doing this, by hand, one at a time. The next day, I ask him how it went, he beams that it was done and he worked really hard on it. I run a query to show people who still had the policy, which returned 300 people. I then ran a loop to change them all to the correct policy. Took me about 10 minutes including the query. When I told him this, he was dumbfounded that he missed so many and that I did it so quickly.
Be lazy people, working hard isn’t always a good thing.
6
u/ThatsNooseToMe Aug 11 '20
Lmao this is perfect. It’s why it’s so important too, it prevents errors and decreases time substantially
3
u/silentxxkilla Aug 11 '20
While I agree with being lazy and automating everything, I would argue that it just makes different errors. Fewer of them maybe, but they're not all prevented. :)
2
3
u/CitySeekerTron Aug 11 '20
I've been able to demonstrate the strengths of AAD/Intune, but the life saver today was in tracking down some PCs with some failing activations. We had asset tags and aliases, but one solution was to either scoop through each inventory item to return the owners, or to relate the alias back to an email address.
I'm the resident PS1 dude, so this was my solution:
$inputs=get-content .\inputs.csv Get-EXORecipient -resultsize unlimited | export-csv schooldirectory.csv $schooldirectory = import-csv schooldirectory.csv $finalReport = ($inputs | foreach {$schooldirectory | select alias, primarysmtpaddress | where alias -eq $_}) $finalReport | export-csv ComputerOwners.csvI created a pivot table to group the duplicate items (things like "shared PC"), and then filtered out the noise ("Student", and other generic account names that mean nothing but which will return an email address), and basically had a list of contacts in under 15 minutes for our director to kick off.
It feels great to be able to wrangle this kind of data and deliver it quickly.
-2
u/ShrykeAbysmal Aug 11 '20
I agree with the final premise, but that could also have been done in VBScript or VB accessing LDAP as well. People have been automating Windows with one thing or another since DOS batch. I don't think the statement that it is a must to administer Windows reflects reality.
2
u/I_ride_ostriches Aug 11 '20
It is for anything related to O365/azure. Sure you can now make graph calls, but I’m not aware of a way to use modern auth with VBScript
-26
Aug 10 '20
[removed] — view removed comment
17
u/galoryber Aug 10 '20
I'm sure they are serious, and I completely agree. Power shell is already cross platform, since V6 and 7 are built in Net core. No win32 apis of course, since that would be Net framework, but I love the idea of writing one script or tool and being able to drop it on any machine. I'm hoping it gets to a point where .net core is a default install and cross platform software could be a single code base. Powershell adoption in Linux is already started and with any luck will continue.
6
u/CitySeekerTron Aug 10 '20
Thank you!
Bash is a shell for running commands and piping wads of output to other commands - functional, with layers of workarounds and hacks built to support it, but ultimately prone to a lot of case-by-case handling of each output that is ultimately accepted as routine. Generally speaking, PowerShell runs functions that return objects that you can bend, twist, and shape in many different ways with fewer tools to gunk it up. I will howeve concede the point that there are some consistency issues that should get resolved as it continues to evolve.
For what it's worth, I'm already loving the partial experience of cooking up bash scripts, pilot testing the outline using Windows/Linux before pushing them onto MacOS for use by our enterprise fleet management software (which is, sadly, not azure. Yet.)
It's also handy to have the ability to use PowerShell on a Mac to manage Windows devices and services.
PowerShell is the way.
2
u/onlynegativecomments Aug 11 '20
You can’t be serious?
I am
Like on Linux?
Why not? I use it on W10, Mac OSX, and Raspbian - write once, run many places.
Why would I want a bunch of arcane win32 functions on another OS?
I can see you're a man of knowledge and experience.
33
u/DnS101010 Aug 10 '20
I use PowerShell every day. You can automate work with it. For a lot of thinks I would have to use my mouse and repeat it. With that language I can script what I need and the server or my computer does this job for me. It is also really powerful. And this language is really descriptive.
On the other hand I use scripts for linux servers. I also like to script with bash scripts. In the linux world the functions aren't that descriptive but the functions there are really powerful and sometimes dangerous.
Nonetheless someone needs to know what he or she is doing.
I love both worlds and I am glad that I can do my work with these tools.
14
u/0elk4nn3 Aug 10 '20
Im in the stage where I want to get used to powershell because I just dont want to use the damn point and click adventure all the time.
Line of code/Script or some one liners and it's done. I freaking love this.
And this powershell thing will not go anywhere since you can do things with Servers SQL gpo AD and stuff REMOTELY
Get good at it and your job is secured for another 30years
34
u/a6zj6 Aug 10 '20
I love it but it seems most of my coworkers are too lazy to learn it. I’m discouraged to use it at work because no one else knows it and thus cannot support it. Such a wasted opportunity.
I’ve used it extensively to solve all kinds of different problems. I love that it’s object-oriented.
15
u/Kildor Aug 10 '20
My work didn't like the fact that I took it upon myself to learn PowerShell until I pointed out that I can verify an account is locked, unlock the account, set a out of office message in exchange and automate installs. I know these are basic tasks but I am learning more and more every day. I do not see it going away.
2
u/somewhat_pragmatic Aug 10 '20
My work didn't like the fact that I took it upon myself to learn PowerShell
Why on Earth would they be upset that you bettered yourself on your own at no cost to them and radically increased your potential for productivity?
1
u/Kildor Aug 11 '20
The main reason is because no one else wants to take the time to use what I've learned or refuse to learn it.
1
u/infinit_e Aug 11 '20
I was in this same boat. I was actually scolded for teaching it to the new help desk staff, and sr help desk guy after I was promoted to Sys Admin (over the guy who had been there several years more than me). I got out quickly after that.
1
2
u/Rearviewmirror Aug 11 '20
That would eliminate 1/3 of my department.
1
u/alinroc Aug 11 '20
It is difficult to get a man to understand something, when his salary depends on his not understanding it.
Upton Sinclair
IOW, their mindset is "why learn something that will automate me out of a job?"
7
u/alinroc Aug 10 '20 edited Aug 10 '20
I’m discouraged to use it at work because no one else knows it and thus cannot support it.
Do it anyway. Prove that it's better. The rest can either evolve or die.
And if the organization insists upon staying in the past, find another one where your initiative is understood and appreciated.
0
u/omn1p073n7 Aug 10 '20
I'm the "powershell guy" at work and it's making really easy to rise above all the guys who won't learn it. We have a guy who still does everything in bash ffs.
2
u/BlackV Aug 11 '20
nothing wrong with bash. pwsh in linux world is still a little way behind
1
u/omn1p073n7 Aug 11 '20
Oh shit i guess didn't mean bash. i meant windows cmd .bat files and shit.
2
1
0
Aug 10 '20
[deleted]
22
u/Inaspectuss Aug 10 '20
THIS THIS THIS. Seriously, it has been the most valuable skill I have ever learned and the time you can save with it is insane. At my previous job, I was the only person who had a grasp of PowerShell and it made me a go-to employee. At my current job in a much larger enterprise, I am no longer the only one who can write it, but I am one of the few who can write it in a clean, organized fashion and not just strip scripts off Stack Overflow and modify a few variables here and there. You will thank yourself later on.
11
u/exccord Aug 10 '20
and not just strip scripts off Stack Overflow and modify a few variables here and there. You will thank yourself later on.
Unfortunately this has been one way that I have been able to teach myself how powershell scripts operate and how to best write them. Not everyone learns the same though. I have so many powershell related e-books that I bought and have not read a single one. I simply cannot learn just by reading a book, I need interaction.
9
u/Inaspectuss Aug 10 '20
And there is nothing wrong with that. That’s exactly how I learn as well. My issue is with the people who never bother to truly learn it. People who have dozens of scripts that are just cobbled together from multiple SO threads, with differing writing styles that make it all too obvious. I mean, it’s great that they’re at least willing to use PS, but it shouldn’t be how you operate long term.
6
u/Raymich Aug 10 '20
Agreed. Find a small problem and solve it with Powershell, don’t walk away until you have it working. Rinse and repeat until you master it.
I’ve only read quarter of the book and been writing scripts for 3 years now, thanks to sites like stackoverflow.
4
u/Dogezon Aug 11 '20
PSKoans (https://github.com/vexx32/PSKoans) is also a great tool for learning PowerShell. And if you have an L&D department, or a charasmatic engineer, you can use this learning course here as an introduction: https://github.com/Sudoblark/Powershell-Intro-Training
A slight plug as I made the course and have contributed to PSKoans. Another great tool is https://underthewire.tech/.
Overall if you learn the LANGUAGE, rather than how to solve specific problems, you'll find that nothing is impossible with PowerShell in the Microsoft space :D
4
u/exccord Aug 10 '20
Couldnt agree more. My sys admin role has me learning and utilizing powershell more than I ever have in the 6+ years at my last place of employment. So far in the 8 months that I have been here I have been able to automate a handful of processes all of which I have scheduled accordingly. I do have some limitations from time to time when I have to get certain elevated privileges from our senior security admin. The one thing that I would like to get going once I can find the time to do so is to be able to manage a hybrid O365 through PS. Still trying to understand that portion of it but haven't been too successful partly because any time I need to snag a module, I need the elevated privileges to be granted to me by the Security admin.
1
u/ka-splam Aug 11 '20
I simply cannot learn just by reading a book, I need interaction.
https://github.com/vexx32/PSKoans - learn by fixing slightly broken or unfinished code examples.
8
u/aaronsb Aug 10 '20
I actually did that (to some extent) and it was incredibly disruptive to the status quo.
4
u/infinit_e Aug 11 '20
Good! “That’s the way we’ve always done it.” is absolutely toxic to improving work conditions and streamlining flows.
15
u/ginolard Aug 10 '20 edited Aug 11 '20
This. Absolutely this. Any Windows admin these days who doesn't know (or at least want to learn) Powershell is a dinosaur. No matter how young they are
7
u/eastlakebikerider Aug 10 '20
Either learn powershell - preferrably as it relates to Azure, or learn how to ask "Do you want fries with that?"
3
u/orwiad10 Aug 10 '20
This is were I am rn. I'm working on putting the junior cisco guys out of work and the cyber security guys for sure.
11
u/BlackV Aug 10 '20
powershell?
powershell thats built into every single version of windows?
powershell that being actively updated currently?
what exactly to you think is "powershell"? maybe that'll make your question clearer
I believe the theory is that 7 (or 7.1 or something) will bring powershell (5.1 which i what I think you're talking about) and powershell core back in line with each other
(although lets be honest here it's not going to be until 8 that it get close to this)
1
u/KBunn Aug 11 '20
Not just every version of Windows, but every app that MS produces, pretty much. Basically all the admin interfaces are via PS, even if there's an "app" masking that. It's a PS world, and MS just lives in it now.
0
Aug 10 '20
[deleted]
2
u/BlackV Aug 10 '20
Fully aware. But not all things work with it. I still require the use of 4/5 for some cmdlets
Additionally 7 is a side by side install so right now does not "replace/upgrade" PowerShell like 2 > 3 > 4 > 5 did
2
u/TheIncorrigible1 Aug 10 '20
Fully aware. But not all things work with it. I still require the use of 4/5 for some cmdlets
Like..? The shim is almost literally just winrm to the v5.1 session.
Additionally 7 is a side by side install so right now
It always will be. It's definitely an upgrade.
2
u/jborean93 Aug 11 '20
Because the shim runs the code in another process, any objects that are outputted are done so with serialisation. This means you cannot invoke any methods on them and the properties are effectively just a snapshot at the time of serialisation. I agree that the compat layer works fine in most cases but there are some definite downsides to it.
0
u/thebeersgoodnbelgium Aug 11 '20
SQL Server SMO has not been entirely ported to core, so there are SQL-based commands that workin 5.1 that do not work in 7.0 :( Same is true for SharePoint CSOM, or it was true when I was working with it last year.
9
u/eastlakebikerider Aug 10 '20
Not sure how you can say it's unknown, unless you're speaking from a development perspective. From the SysAdmin perspective, you're not qualified to be a Senior Sys Admin unless you can automate most junior admin functions with it IMO. Also, there's a lot of advanced O365 and Azure functions that you can't even do with a GUI which really make powershell knowledge a requirement, and no longer just a nicety.
9
u/F0rkbombz Aug 10 '20
First, a lot of statements in OPs question are misleading, and I don’t think they are accurate.
My thoughts - you either learn Powershell as a Windows / M365 Admin or you’re going to be replaced. If you want to get into Pentesting or Security not knowing PS is going to limit your abilities on a Windows network.
It isn’t going anywhere, will likely only expand its capabilities, and it speaks volumes about the person if they haven’t heard of it or regard it as “janky”.
2
u/alinroc Aug 11 '20
My thoughts - you either learn Powershell as a Windows / M365 Admin or you’re going to be replaced.
It goes far beyond Windows and M365/O365. If you're working with any Microsoft products, you're either learning Powershell or being left behind. Azure DevOps. SQL Server. You name it.
1
11
u/thatto Aug 10 '20
It is the duct tape of the Microsoft administration tools.
It is not going anywhere unless Microsoft pivots it's focus to some other technology.
> it feels like most people don't regard it as particularly valuable in the long term.
What people?
10
u/MrTechGadget Aug 10 '20
PowerShell 7 (core) is great, I use it constantly from Windows, Mac, and Linux. Since it is being actively maintained, constantly developed upon, supported my countless vendors, it will continue to be a very valuable tool for a long time.
5
u/EIGRP_OH Aug 10 '20 edited Aug 11 '20
I don't think its going anywhere seems like its actually rising in popularity. I can say personally, I'd be a lot more hyped for newer versions and its features if they would start shipping it with Windows.
5
Aug 10 '20
Anybody who thinks powershell is a low-code/no-code environment has probably never evaluated one of those tools. I don't know who you're running with that tells you that powershell isn't useful, but they are dead wrong. As long as there are businesses running windows, powershell will be super useful.
2
u/CoryBoehm Aug 10 '20
Agreed. Seen a bunch of different languages/tools in my time and the complexity commonly seen in PowerShell is definitely on the more complex end of coding and reminds me a lot of C/C++. The flexibile typing and the somewhat weird at times chaining of language commands.
2
u/nielsenr Aug 10 '20
Never mind the fact you can interact with anything that is managed by CIM, WMI, or dotnet, and create custom classes.
7
u/Cyber7a Aug 10 '20
I use it just about every day. It makes routine tasks much simpler. And for big jobs? I wouldn't want anything else. Just today I updated and ran a script to find orphaned computer accounts. I would NOT want to do that by hand when talking about 3000+ computer accounts. With powershell it took maybe an hour initially to write the script a few years ago and about 10 minutes today to make a few tweaks to get some additional details out of it.
Also, I have demonstrated PS to several colleagues here. While all at least appreciate it, a few have embraced it and are learning/writing their own scripts.
3
u/ultimattt Aug 10 '20
That’s like asking if Bash is going away, sure there are more Linux admins using it vs windows admins, but really?! You want to go back to vbscript? Or cmd with pre compiled binaries? Nah fam.
Powershell is super powerful, and it’s the basis of anything Microsoft anymore if you want to do it effectively and efficiently. I wish I had more time to get into the expanded modules - I haven’t been using as much since my focus is different nowadays.
3
u/Rattlehead71 Aug 10 '20
Powershell 7 is great. I wrote and tested a pwsh azure script on my Win 10 workstation, uploaded it to my Zabbix (Ubuntu 18.04) server, and it ran perfectly. It's here to stay for a long, long time.
3
u/thePowrhous Aug 10 '20
I agree with some of the comments I've seen skimming through here. I'm sort of confused by OPs comments that's PowerShell feels 'janky' and worried about the future of the language? Now don't get me wrong, OP, you are obviously entitled to your opinion and this is supposed to be place to share ideas, debate topics, etc.
With that being said, to paraphrase Don Jones... "Learn PowerShell or learn, "Would you like fries with that?". Now this obviously being specific to a Windows heavy environment, but nonetheless, true, and even more so since it was said years ago.
We recently had this discussion in work as we have been seeing a culture and job shift where those Admins and Engs that don't currently know PowerShell (automation or general CLI workflow) are starting to be typecast into generic Desktop Support roles.
While on the subject of job roles, I myself am in the process of taking what I've learned over the years as a Sys Engineer and now migrating to a DevOps/SRE engineer. If anything, I found that again, mainly in a Windows / Azure environment, if you don't have a deep understanding of PowerShell in the various ways it can be utilized in a Windows environment (basic commands/scripts/functions (adv functions)/modules, module development, PowerShell DSC, scripting ARM within Azure, etc.) you're next to screwed.
3
u/AWDDude Aug 10 '20
I use power shell for allot of automation at work, and even use it in my home lab. I am probably the best and most experienced person at my company with power shell. It can do almost everything .net can do. But the language has some problems that need to be addressed: First, it needs to be a better concurrency/scope model. PSJobs are easy to create but they have massive overhead and take forever to spin up. Each Psjob or runspace is treated like its own separate scope and it is very difficult to share anything between your runspaces. Second, more uniformity, for syntax, for scope, even runtimes. I don’t know how many times I have run a script in debug and then it not work when running in power shell runtime. There are some instances where scope works differently between debug and actual powershell.
5
u/AybaraAlthorPeregrin Aug 10 '20
I think as infrastructures expand and become more dependent on code you’ll only see more adoption of powershell. Yeah it’s really unlikely to catch on in the Linux world, but every self-respecting sysadmin ought to know at least the bare minimum of shell knowledge, for both windows and Linux.
Curious tho in what ways Powershell remains janky? Powershell core aside, v5 is incredibly robust and I’ve yet to run into any groundbreaking issues in my work.
1
u/TheIncorrigible1 Aug 10 '20
I think it's a reference to its breaks with the "norm" in scripting languages. Its function syntax (which is really cmdlet syntax) and such are really beyond the weirdness threshold for some as a C-inspired syntax language.
4
u/ihaxr Aug 10 '20
Assuming you're talking about PowerShell Core, eg: the only currently maintained version of PowerShell... it will not going anywhere for a very long time.
Literally running a script right now because someone moved a folder into another folder on a gigantic drive...
[System.IO.Directory]::EnumerateDirectories("E:\share","*TopLevelDirectory*",1)0
Aug 10 '20
[deleted]
2
u/ihaxr Aug 10 '20
It's completely true. Supported is not the same as maintained. Yes, it's still going to be supported because it's built into the OS, but they're not adding any new features to it or fixing bugs, so it's no longer being maintained outside of potentially fixing major security issues.
0
Aug 10 '20
[deleted]
2
u/ihaxr Aug 10 '20
If it makes you feel better, sure. PowerShell 5.1 is so great it will be supported and used forever and ever. Seriously, what a weird flex.
4
u/zulu20 Aug 10 '20
I’m the PowerShell guy at work. Everyone starts somewhere. Just learn how to one thing, then another, and another. Before you know it, you’ll be the PowerShell guy too. The more you use it, the more things you’ll figure out you can automate with it. Then you’ll look back at things you’ve written 6 months ago and can’t believe the crap you used to write. Just like anything else, the more you use it the better you’ll get.
2
u/zenyl Aug 10 '20
I view pwsh as an underappreciated gemstone. It definitely has its limits, however it's an amazingly useful tool for a ton of scenarios.
While I initially just used it for managing 365/spo/az, I now use it for anything I just want done quickly, without needing to create a new C# project. It also comes in handy in conjunction with C# development, as it works nicely for quickly testing things, build automation, etc.
Pwsh will never be as popular or widely used as Bash, but it's far from useless and far from legacy. I personally think it has its golden age ahead of it.
2
u/j1akey Aug 11 '20
Jeez I have no idea what this is all about. PowerShell indisputably one is the most important and useful tools I have at my disposal.
3
Aug 10 '20
I use it every day personally and professionally. Don't see that changing any time soon. Especially with ServiceNow Orchestration + Powershell - automating onboarding / offboarding / ad / exchange / azure / devops /etc. I've made everything from PDF Generators to video game bots with it lol.
1
u/229-T Aug 10 '20
Do you think it's legacy and will be deprecated in the foreseeable future
No way in hell. Powershell is a fairly widely compatible, low-barrier-to-entry tool for task automation and tool-making. It's bridging the gap between programming and the technically-adept non-programmer in a world that is evolving to desperately need that.
1
u/AnOkayBoomer Aug 10 '20 edited Aug 10 '20
Powershell's future is Windows future.
Will it be depreciated? No. Even tons of things that seem like replacements to PowerShell use PowerShell under the hood. It's way too entrenched for a company like Microsoft to strip it out.
>it feels like most people don't regard it as particiuarly valuable in the long term.
I've run into this opinion before but I have yet to meet somebody who holds to this prejudice once they realise you not only can't do things as efficiently but that you can't even do things on Windows without PoSH.
0
u/Disasstah Aug 10 '20
What's/where is a good way to learn it? I need something to show me practical applications for using it.
2
u/snoopy82481 Aug 10 '20
There is a really good book series called “powershell in a month of lunches”. It should get You started.
1
u/blaughw Aug 10 '20
Administer Office 365. Learn about PS for Exchange, Azure AD, Active Directory (on-prem), Skype/Teams, Sharepoint workloads.
1
u/Disasstah Aug 11 '20
I didn't mean actual applications, I meant practical uses for PowerShell.
2
u/thebeersgoodnbelgium Aug 11 '20
At home, I use PowerShell to import CSV files into Spotify Playlists and setup my own DynDNS knockoff that works with CloudFlare.
At work, I've migrated entire SQL Server instances and automated security scanning and remediation processes. Offloading audit files, automatically renewing letsencrypt certs, scanning windows catalog and automatically downloading & installing KBs. Once you realize the potential, nearly everything can be automated.
0
u/aaronsb Aug 10 '20
Extend PS Core to fully administrating Linux and I think there will be a very long term legacy to it's future.
-2
u/serendrewpity Aug 10 '20
I think they'll push it and push it until far too many engineers have a minimum of a above average proficiency in it and then they'll abandon it and discontinue support
-3
u/raptr569 Aug 10 '20
I'm a big advocate for PowerShell but it is really inconsistent and I have to spend a lot more time googling snippets than I do other languages.
-3
u/blaughw Aug 10 '20
The things that are janky about Powershell in Windows are:
Cmdlet syntax, sometimes something like this:
Set-mailbox -identity [email protected] -allowSetting $true
Will in fact need to be set like this:
Set-mailbox -identity [email protected] -allowSetting:$true
Usually, these types of syntax things are at least consistent in a workload, like Exchange.
Then, there is cross-platform jankiness, like the fact that many Authentication libraries still rely on binaries and DLLs and are therefore windows-only. Many of the ones I deal with most (Azure and O365) are coming along in a cross-platform way.
0
Aug 10 '20
[deleted]
2
Aug 10 '20
[removed] — view removed comment
2
u/alinroc Aug 11 '20
Actually, there are some cmdlets that you have to do that syntax on
Then that's a problem with the individual modules, which are the responsibility of each product team. It's not Powershell itself at fault here.
0
Aug 10 '20
[deleted]
0
Aug 10 '20
[deleted]
4
u/_benp_ Aug 11 '20
Anything you're still doing with bat/cmd/vb are easily replaced by Powershell. The language is simpler, more intuitive and more tightly integrated with Windows and MS products across the board. It has support from major players like VMware and NetApp.
If you're still maintaining legacy scripts instead of updating them, I would venture to say its because of laziness or neglect within your organization.
2
u/TheIncorrigible1 Aug 11 '20
its because of laziness or neglect within your organization.
Or option 3: complexity/cost of replacement. I once ran across a string of batch scripts that was hundreds of LoC each and made CALLs to others as "modules." It was quite a sight to behold, but replacing it would've taken months to implement that we didn't have
-1
u/ShrykeAbysmal Aug 11 '20
I can't imagine why anyone would think it's simpler than vscript/wscript.
4
u/Hanthomi Aug 11 '20
I can't imagine how you would NOT think so?
Seriously, fuck vbscript.
3
Aug 12 '20
Lol my coworker HATES powershell.
Even changed his PS header to read as so.
When I was first learning scripting, he was wanting me to learn vbs. I for the life of me could NOT figure out how to and when I learned PS, why would I want vb? PS is easier and less lines of code. Oh and actually supported by MS.
1
u/Hanthomi Aug 12 '20
Sounds like a dinosaur trying his best to become obsolete.
I'll shoot down anyone trying to put new vbscript crap in production.
1
u/methos3 Aug 12 '20
I love PowerShell and have been using it since 1.0. But I admit it can be a steep incline at first. I still switch up the parameter syntax difference between calling cmdlets and .NET methods (methods use commas and putting each parameter on its own line doesn't require a line-continuation character). And the pipeline took a bit to get used to.
0
u/MrTechGadget Aug 11 '20
Zombies, just because they are still used doesn’t mean the language isn’t dead.
0
Aug 10 '20
[deleted]
0
Aug 10 '20
[deleted]
0
Aug 11 '20
[deleted]
1
u/TheIncorrigible1 Aug 11 '20
The problem I ran into when I did do consulting was stability. I have a family to support at this point. But, I do "DevOps" in my dayjob, I just double as an appdev about half the time.
0
Aug 10 '20
[deleted]
1
u/Nanocephalic Aug 11 '20
If you don’t think linuxland has quirky decisions in place to keep backwards compatibility, then... I dunno, man.
-15
98
u/[deleted] Aug 10 '20
What? It's arguably the most important feature in Windows since having TCP/IP built in. Either you're not aware of the amount of foundation Microsoft has built with PowerShell or you're trolling. Almost all of their backend products feature PowerShell interfaces for automation and management: Azure, Exchange, SQL, Skype, ADFS, IIS, and on and on. A huge amount of 3rd party vendors support PowerShell as well, i.e. VMware and Citrix to name a couple.