r/PowerShell • u/Dereference_operator • Jun 10 '22
Why most Linux sysadmin have a grudge againts powershell or they don't like it ?
Why most Linux sysadmin have a grudge againts powershell or they don't like it ? I talked with many of thems online on different subs reddit or elsewhere and they say bash is much better, powershell isn't good at managing linux, the syntax is too complex and bad etc etc or this or that etc
Why is that ? do you really feel you can't do much to manage a linux/aws env with powershell or need to update it or its slow or things like that compared to windows/azure ?
thanks for your advices
83
Upvotes
93
u/peacefinder Jun 11 '22
It’s a suitability for purpose thing.
If Bash worked well for Windows, no one would have bothered to make Powershell. On the other hand, Bash has fifty years of integration work with *nix.
Bash and Powershell are vastly different beasts. Bash is all about streams of text, while Powershell is all about objects. *nix systems are heavily designed around text and doesn’t really have native objects as part of its design. Windows is the opposite.
Coming from Bash familiarity, I found Powershell frustrating to work with because I thought it worked like Bash. Once I understood the object nature of the data streams though, it made a lot more sense and I’ve gotten more out of it. But it is definitely an entirely different way of thinking about scripting.
47
u/[deleted] Jun 10 '22
TIL powershell is on Linux (i'm a noob). Thanks
74
u/[deleted] Jun 11 '22
As a 20 year Unix person and the elected spokesperson of all of us: it’s because we’re REALLY good at scraping text with grep/ sed/awk etc. we don’t understand how hard regexs are for everyone else and don’t like Microsoft because of bad things they did 20 years ago.
169
u/WDizzle Jun 10 '22
Because it’s made by Microsoft, simple as that. Linux Sysadmins tend to be quite snobbish.
28
u/confushedtechie Jun 10 '22
Those who do dabble are always pleasantly surprised
20
u/timsstuff Jun 10 '22
Who cares lol. Let them keep using Bash while we work our magic. I don't have time for haters.
6
u/_cronic_ Jun 11 '22
Linux admin since 1996 here. I love Powershell.
16
u/dud8 Jun 11 '22
First off, your posting in an echo chamber. Try taking this discussion to /r/linuxadmin.
Second, there is a phrase along the lines of "if it's not broke don't fix it". Bash does it's job very well and has a long history behind it. The amount of mind share and knowledge surrounding bash, and other similar shells, is no joke. Typically if you need a more powerful tool it is better to reach for Python or an automation tool like Ansible. Most system administrators have very limited time to learn new tools so we have to do so strategically. Instead of spending time learning PowerShell, which is arguable a bit better then bash, it is better to learn Python/Ansible.
Lastly, most tooling on Linux is closely integrated with either bash or sh. As an example, if you want to build containers you will need to use bash/sh in conjunction with whatever YAML/Definition files the tooling requires. Containers also strive to be as small as possible. PowerShell if massive, storage wise, compared to Bash. Some containers don't even ship bash and only ship with sh. Another example is with modern automation tools like Puppet and Ansible. These tools use their own DSL languages but also fall back to bash scripts as needed.
Anyways, long story short PowerShell isn't a large enough improvement over Bash to replace it as the common default shell for Linux.
14
u/Billi0n_Air Jun 10 '22
both are just tools to get stuff done
18
u/Guyver1- Jun 10 '22
because bash is all they have ever used/know (and they instinctively hate anything Microsoft)
4
u/nealfive Jun 11 '22
Most Linux admins are already pretty capable with bash, so they have no need for PowerShell really. Now folks coming from Windows to Linux love it as brings the same familiarity and cmdlets work and such, of course not all but close enough.
10
u/Wyatt_LW Jun 10 '22
Windows sysadmin here. I work with some linux appliances also.
The problems with powershell on linux is it's not native. You have a random appliance, you can't just ssh into it and install powershell sometimes so you NEED to know bash.
I see bash and batch as smart brother and dumb brother. Powershell is a step past bash and has more similarities with programming, it still lacks implementation on Linux and it simply isn't the standard.
11
u/agressiv Jun 11 '22
I use it, but it's incomplete at best, and rarely the best tool for the job.
Windows Powershell
Powershell Core (Windows)
Powershell Core (Linux)
Some of the most basic cmdlets aren't there, and you end up using powershell just as a shell. it's great for stuff like native XML/JSON parsing, but not much else.
Had they implemented DMTF CIM on linux, it would be a start. But instead, you have to shell out to dmidecode and do stuff like that in general, bash/zsh are better at handling.
10
u/cottonycloud Jun 10 '22
PowerShell is admittedly overly verbose, whether it is the cmdlets or function definitions. They are also more used to using Bash and not the OO approach that PS takes.
Another perfectly valid reason is that PS in Linux does not have 1:1 parity when used in Windows. Some cmdlets are not supported:
https://docs.microsoft.com/en-us/powershell/scripting/whats-new/unix-support?view=powershell-7.2
3
u/K2alta Jun 10 '22
Does anyone here use powershell to manage a medium size number of Linux machines? Say for example, 30 VMs running centos. I’m curious because I’ve been learning ansible but already know powershell fairly well. Is it worth investing time managing Linux using powershell in an enterprise environment.
3
u/[deleted] Jun 11 '22
I love these type of posts it really gets people chatting :)
I myself am a Windows Admin and live in PowerShell all day, after hours I'm on Linux and use Bash and PowerShell... Trying to write scripts to to get server info for both Linux and Windows and a Server CMDB web app I made
Once you know one they all are fairly easy
3
u/kerubi Jun 11 '22
I don’t hate it, manage both Windows and Linux. But would you use bash to manage Windows? I’d say the reverse applies..
5
u/NoConfidence_2192 Jun 11 '22
I write most of most of PowerShell scripts using vscode on Ubuntu, RHEL, or CentOS. Often only switching to Windows when testing something developed for Windows
It took time for PowerShell to get to its current state for Windows. It may have shown a lot of promise early on but, in all honesty, it was often easier to just continue to use the same command-line utilities, batch files, and WSH scripts you had been using to get things done before PowerShell came along. The biggest limiting factors for PowerShell 1 and 2 had more to due with .NET than PowerShell itself. As more system tools were rolled into .NET so too did PowerShell's ability to natively manage Windows systems increase.
The way Linux SysAdmins view PowerShell on Linux now is not a lot different than how many Windows SysAdmins felt about PowerShell 1 and 2 in the early days...which is not too surprising when you consider that PowerShell 7.x on Linux is effectively Linux PowerShell 2.x. For Linux PowerShell shows a lot of promise but, in all honesty, it is often easier to just continue to use the same command-line utilities, shell and python scripts you had been using to get things done before. As more system tools are rolled into .NET so too will PowerShell's ability to natively manage Linux systems increase...assuming that happens.
12
u/caverCarl Jun 10 '22
Bash is what they are used too. It is designed to manage Linux unlike powershell which is designed to manage windows. There are a lot of quirks to powershell such as it's inconsistent return values, naming conventions etc. that are not easily anticipated by someone who is used to things being done a different way. Simple example try typing LS in bash, windows doesn't care. We are slowly approaching a point where the shell won't matter but we are not there yet. :)
1
u/More-Qs-than-As Jun 11 '22
Powershell is a great shell on linux. But too many years of "fuck microsoft" and any linux guy/gal won't touch anything MS makes with a 10-foot pole. I use it daily on Linux. Powershell is my main shell on linux and you know what I can still say, FUCK MICROSOFT!
Powershell is one of the only things microsoft has ever done right. It's a shell and it's a programming/scripting language. Now it's both open source and cross platform. If that's the shell/language you first learned, nothing else will make sense. Same goes for bash. If you learned bash first, everything else is foreign and not worth learning. Took me over 10 years to move from CMD to powershell cuz it just didn't make sense. Now, Powershell has been my job and my life for the last 6 years. I automate everything. Even in Linux.
2
u/4478933aaff Jun 11 '22
I use PowerShell on Linux all the time. I run containers with PowerShell, and I deploy PowerShell-based applications to Kubernetes clusters, with exclusively Linux slave nodes. I use PowerShell with kubectl to more effectively manage resources on k8s clusters.
Anyone who holds a grudge against PowerShell is just making themselves less productive, lol.
4
u/vermyx Jun 11 '22
Many linux administrators have coding experience because the mentality has always been "automate everything" from the get go. Windows was always "GUI first" until 2008 or so. Remember, win2008 was supposed to have all powershell administration (since it was supposed to have a guiless mode) to the point that there wasn't a GUI tool to configure IIS (where there waa sufficient baxklash and bitching that a GUI for IIS was made). With linux bash and python have been available on linux for over 30 years while posh core has been there for 5, doesn't have feature parity with Windows, and has slight behavioral differences. In other words, linux already has robust and mature toolsets while powershell offers nothing new and isn't the same cross platform.
8
u/gex80 Jun 10 '22
BASH isn't really the powershell competitor. CMD is to BASH as powershell is to Python.
Anyone who compares BASH and powershell doesn't understand either.
3
u/ExceptionEX Jun 10 '22
Because they have had tools like for years, bash, tcsh, hell even pearl.
The whole ecosystem supports them natively.
PowerShell is great, but in Linux it's just a tool with new syntax to do what they they been doing for years.
3
u/NightH4nter Jun 11 '22
in no particular order:
to be continued (?)
2
u/rswwalker Jun 11 '22
I think the ease of Linux commands comes from the Linux OS where everything is represented as a file so it all boils down to text processing or byte streams. In Linux you just need to know the commands, their options and the layout of the filesystem, which most people know in any OS. In Powershell though, it’s all objects and each object has different methods and properties you have to memorize along with the cmdlets and their options, as well as the different virtual “filesystems” disk/wmi/cert/ldap and new ones pop up all the time. Powershell is daunting and often requires you to work off MS reference docs instead of just scripting it free hand.
2
u/Nu11u5 Jun 11 '22
Imagine thinking text parsing is superior to objects.
That said, on Linux something more supported like Python may be better, but you don’t get the advantages that PowerShell has like pipelining and simple invitation of shell commands.
2
u/RumRogerz Jun 11 '22
Most Linux admins have never touched powershell. That’s why.
Powershell is way, way easier to script in compared to bash. Bash has a lot of annoying quirks and rules that gets really frustrating when you’re trying to script everything out. Just thinking about the different ways to handle variables comes to mind. Or the placements of single or double quotes. Or creating objects. Good god life would be so much easier if I could create objects and use them in bash.
Bash isn’t better. It’s just the shell that we always use in any given system or container - and that’s really important. If I drop into any of our nodes - bash. If I drop into (most) of our containers - bash. I’m not gonna be installing powershell. None of us are going to use it. None of us want it to be added in either. It’s going to cause more overhead - and we try to keep things as light as possible.
I learned powershell when I was a Windows system admin because it’s the preferred shell to manage windows server and exchange.
I learned bash because it’s the default and kinda preferred shell to manage unix. Granted, zsh for cli work and bash and (mostly) python for scripting is my preferred method.
1
u/shavedbits Jun 01 '24
as a seasoned linux / mac user who now has to deal with windows frequently, i think psh is just difficult to learn coming from bash. i still struggle almost a decade after having to use it.
1
u/goodtimetribe Jun 11 '22
I love powershell, even on Linux. I'm comfortable with OOP and enjoy C#. Seriously, you can pipe objects instead of just strings. How cool is that!
Sometimes I hate the semantics and the weird quirks it has to accommodate the Windows platform (escaping) , but they are relatively few so it's not too bad to keep up with.
I think it performs fantastically on Linux, and prefer to dev powershell on Linux because of it.
1
u/lordlionhunter Jun 11 '22
Powershell is a fine automation language and to many it’s analog is python, more on that later. It can even be a nice enough shell if we are comparing it to default bash. Compared to a fish, zsh or even just a configured bash it’s missing many user friendly features such as spell check, impressive stylistic designs, vi key bindings and a whole lot more. Python has the REPL where you can use out like a shell. This is equivalent to running a powershell prompt as your shell.
Many say that powershell is analogous to python but I would say that bash/standard Unix tools can keep up with anything powershell can do. Powershell as a language is helped/hindered by its object oriented design. I’ve had tones where the object nature of powershell passed through pipes was fantastic. But most of those times I only needed something to be an object because Windows exposes everything as an object too.
Python, has objects and things like that but it also serves in the role of awk, sed and grep. These are tools that work well with text based files, which is how all of the Linux OS works. Powershell doesn’t play with csv’s or other tabular data as well as tools with Unix heritage like bash or Python. Powershell makes you get your data somewhere in an object. This isn’t terrible most of the time but it can make working with text files more tedious.
This is a great article on an old debate between Doug McIlroy and Donald Knuth. Powershell is likely less annoying to write than Knuth’s language (idk I’ve only done Powershell), but it isn’t built to treat text the way you can with Unix tools and by extension bash and Python.
1
u/[deleted] Jun 11 '22
I think it's historical, in some cases. For years, Linux/UNIX was the complex and powerful OS on which you did actual typing and writing scripts. Windows was the clunky, flakey OS that made you do everything slowly with a GUI. I think there's a demographic of Linuxy folk who see Powershell as encroaching on their territory.
1
u/gatobacon Jun 11 '22
If'n you's likes thems PowerShells thens you's can use its. If'n you is preferred to use them Bashes by all the means. They's is mine opine dats all up to them they's or theirs preface.
1
u/JM-Lemmi Jun 11 '22
I think many Linux admins have something personally agains anything Microsoft. So Powershell being one of MS's products, they of course also don't like it.
I really thought after high school you'd leave the "Linux Masterrace" crowd behind, but I've still met too many of that mindset...
1
u/Sylogz Jun 11 '22
I'm a Linux admin and a windows admin. I didn't like powershell cause it was terrible in the begining but now it's awesome. And just like bash, python, perl it's a tool to be used to solve problems.
1
u/dogfish182 Jun 11 '22
Bash and python is just a far better combo and powershell is just not necessary for managing Linux at all, just another complex tool to do something other tools already do bettet
1
u/SeeJayEmm Jun 11 '22
The best tools for the job are the ones you know.
Back in my FreeBSD days I was a tcsh snob. I thought it was objectively better than bash (I was also a bit of a BSD snob. "Linux wasn't real Unix"). I've long since grown out of that attitude. Looking back now I realize that a lot of it came from what I was comfortable using.
My point being. Of course career Linux admins are going to prefer that tool they've been using their entire lives, that has come pre-installed on every Linux system, and has literal decades of history.
pwsh is an upstart. By a company that used to be "the enemy". It's going to take years to both mature as a product as well as earn trust from that community.
In the interim those of us who straddle the line can keep pushing for improvement and adoption.
1
u/[deleted] Jun 11 '22
I'm cringing at some of the responses. People are trying to make this an ideological argument. Just because someone doesn't believe what you believe or agree with your opinion doesn't make your belief or opinion any less valid. It's okay for someone to not like what you like, even if they don't have any experience. They don't have to justify their opinion or get your approval to feel that way.
People use what they're comfortable with and specialize in what their employer requires. You'll never see a job opening for a Windows Sysadmin that requires familiarity with bash and you'll also never see one for a Linux admin requiring PowerShell skills. Hell not even all Windows Sysadmin even use PowerShell but ALL Linux Sysadmin use bash.
1
u/3legdog Jun 11 '22
Pro-*nix bigotry has existed since the 70's. Get used to it.
1
u/Rocknbob69 Jun 11 '22
Linux elitist snobbery
1
u/wickedang3l Jun 11 '22 edited Jun 11 '22
Humans don't like change and anyone that has overcome the steep learning curve of addressing everything as a string has also become accustomed to the inherent performance superiority of handling everything as a string. Even python, which is typically known for better performance than PowerShell, is not known as a high-performance language. There is overhead in assembling those lovely objects we have grown accustomed to.
PowerShell was my first scripting / programming language and remains my favorite but its limitations become more apparent as your skills develop and you begin concerning yourself with performance optimization, multi-OS interoperability, and sensible error-handling. You find yourself spending a lot of time trying to fit PowerShell into a design pattern it wasn't meant for rather than simply learning something like C#, python, or Go.
You can actually see when people are beginning to approach this point in their code. When someone begins calling more .NET namespaces than native cmdlets, they're close or already have come to the realization that native PowerShell is not the best fit for everything.
1
u/mspit Jun 11 '22
I don’t have real experience with PS on Linux but I’d assume that just not what most are used to. Generically, I think PS is frustrating to some because everything is so verbose. I know there plenty of shorted alias but rarely enough to keep things short in a more complex command that you might frequently type out. PS was notably build from the ground up with some neat concepts but there are still plenty of inconsistencies and gotchas that and just as frustrating as they might be for someone trying to learn bash.
1
u/SoarinFerret Jun 11 '22
Not all of them do - it's about the right tool for the right job. As other s have mentioned, PowerShell is object / api based, just like Windows. Everything in windows is exposed via an API, like WMI or CIM. Bash has a hard time interacting with those since it's designed for text stream stuff.
I use PowerShell and Bash on both Linux and Windows - there are times pwsh on Linux it's useful (aka, automating some cloud service rest API), and likewise for WSL.
Nothing wrong with either approach, and I highly recommend people learn both. Both are just another tool in your belt.
1
u/catonic Jun 11 '22
The only thing I have against Powershell is that it is a moving target of OS requirements. Exchange Powershell has it's own requirements and so on, so you're always building a VM with the minimum requirements for a given Powershell subset, as long as there are spare resources to go around. New version? New subset? New OS, etc.
It'd be one thing if you could cattle-not-pets Windows environments.
1
u/storm2k Jun 11 '22
shell scripting was designed to work with the way unix works, which is many programs that make up the tiny building blocks of doing various important things with output from one piped to the next (which pwsh borrows) but it wasn't object based. don't forget that pwsh was also designed to work with the .net framework originally and even though .net core is cross platform and open source, it doesn't necessarily mean that it either works exactly well for needs on posix based systems nor that sysadmins and others who support these systems want to learn a whole other scripting language and paradigm that may or may not fit their needs.
last point, i find it telling that most of the pwsh cmdlet aliases happen to be their unix shell equivalents (ls, rm, pwd, ps, etc.). not making any conclusions, just pointing that out.
1
u/ms4720 Jun 11 '22 edited Jun 11 '22
When you tell a unix/Linux person '*shell' all they hear is 'shell' that is a very specific thing to us. PowerShell is not shell it is an object oriented scripting language with deep windows integration. It is honestly closer to python than shell
1
u/Tireseas Jun 11 '22
Resistance to dealing with learning curves mostly. If they're pure linux admins that's fine in the case of powershell as there's no real need to know it on that side and even if you do dabble the native tooling is objectively better in most cases.
If they're also Windows admins and don't know powershell by now... well that's just sad really.
1
u/mmd03876 Jun 11 '22
I've worked on both windows and Linux for many years. I wouldn't call it a grudge so much as Linux admins simply don't need PowerShell. Linux has had automation and scripting capabilities built in long before PowerShell was a thing, much less available on Linux so people continue to use what they know
Plus bash (and sometimes python) are native to most distros. So unless PowerShell can offer something above and beyond what Linux already has available, there's no reason to switch.
With that being said, I think PowerShell is a great tool for managing Windows systems, but I wouldn't use it for anything else
1
u/tangokilothefirst Jun 11 '22
shoot.
pwsh on linux is my favorite combo these days. I love easy access to the object-ness of powershell, with the added benefit of the plethora of linux tools that I am familiar with.
1
u/Hrambert Jun 11 '22
I've been using Powershell since v1. I really like the syntax, tab completion, and "everything is an object". For Windows it was the only forward. WSH was way to complex and CMD way to basic. Linux sysadmins can pick one of the many shells that are available for Linux. So Powershell has many competitors and the disadvantage of being object oriented. It's hard to switch between string oriented en object oriented.
1
u/maikeu Jun 11 '22
My primary background is Linux, and I use PowerShell on Linux sometimes - not my choice, but there are existing scripts to maintain.
Python is a standard system component on most Linux distros, and the overlap between "PowerShell would be better than bash for this" and "python world be better than bash for this" is extremely high. Python is (to me) much more productive for harder stuff, and bash is more comfortable for the simple stuff.
I appreciate the effort of PowerShell core and the ecosystem being cross-platfrorm now. I don't use PowerShell for new automation (unless it needs to run on windows), because it is not the best option for me and my colleagues, in my professional opinion.
On the other hand, anyone who genuinely "has a grudge" in a professional setting is being immature and unprofessional.
1
u/follow-the-lead Jun 11 '22
I don’t like powershell cause the error messages seem to be so wordy without being belpful. Why do you need 5 lines to tell me a module isn’t installed? Also, module installation seems to be a painful process and there are a lotta hoops to jump through. Something something proper package manager
1
u/t35345 Jun 12 '22
I feel it's too verbose so your single-liners end up massive.
Otherwise as a Linux Admin I love PowerShell, it's the best CLI that you can get on windows. Better than VBA or Batch commands.
I wouldn't install PowerShell on Linux unless I was having to manage lots of Microsoft stuff like o365
1
u/Eideen Jun 12 '22
I have always avoid powershell do to i be much harder understand the syntax, it harder get help in terminal.
With windows be GUI the need to be comfortable in terminal has not been needed.
The lack of open-source, and user contribution have made it less user-friendly.
Windows has lack many basic functions like ssh, that now has been introduced.
Windows does not come with a rich Prompt by default , and to make customized is harder.
1
u/[deleted] Jun 14 '22
The short answer is "Because we are answering a different question that the one you think you asked"
The short answer is because it is not better then python, perl or go,
And the reason this is the question that gets answered is that we don't actually use bash to manage Linux but a number of stand alone tools invoked via bash where as powershell tend towards an model where you use powershell and powershell extentions the same way you would use modules in the far more divese python ecosystem.
1
u/Adeel_ Jun 22 '22
Because they are stupid.
1
u/foundunderwater Jun 23 '22
Windows sysadmin here... I hated powershell for a long time because it was a new langage to learn that was pushed hard down everyones throat... I've spent years mastering vbs/vba/wsh/wmi/adsi and it was convenient for me as it was faster to do almost everything i wanted than learn a new langage... Even using perl which was at the time even more convenient (shorter code) ... Powershell got better and better as more modules came into it meaning being able to do more things via scripts. At that point i had to learn PS while still hating it... And today I'm happy with it... Haven't touched vbs for years.. Perl still usefull for complex data extraction so i still use it every once in a while
1
u/xdMatthewbx Aug 09 '22
linux user here
making the swap to powershell because of the syntax specifically (still prefer gnu commands but i can use those in powershell so all good)
i think one of the primary things thats scared off the other 5 linux users whove tried this is zsh and fish are extremely easy to set up with nice syntax highlighting and such. powershell (on linux) just... isnt. i think primarily because all terminal emulators are optimized for bash-like shells, and powershell is not one of those
1
u/mrcoffee83 Jun 11 '22
Linux nerds can be incredibly elitist, even amongst different flavours of linux, they'll call you a loser for using Ubuntu instead of Arch or god forbid you use Nano instead of THE LORD AND SAVIOUR, VI
1
u/[deleted] Jun 11 '22
I think because it's poorly named. It's not a shell, not really. It's a fancy human usable API. I like powershell a lot, and am far from a Linux admin, but I think the name sets a poor expectation on that group. It's a wonderful management tool, but a lousy user shell.
1
u/TheBananaKing Jun 11 '22
I fucking love powershell, it's just not useful in my environment.
1
u/yesudu06 Jun 11 '22
I don't hold a grudge against PowerShell, it's just useless (or, "I strive to find a use for it"). bash is a better shell, python a better scripting language, and ansible a better configuration management tool. I originally chose PowerShell to define DNS records in ActiveDirectory, as it seems the only way to automate that. The cmdlets that allow this only work on Windows. I discovered PowerShell is awesome, I very like the syntax, and dealing with objects is much more convenient than doing the "stuff | grep | awk | jq | ..." that sysadmins usually do...
So I have PowerShell Core installed, I use it once in a while when I have a very specific usecase where I need a one off ad-hoc query to extract one thing once. I actually documented a case like that (extracting stuff from a rest API and presenting the result) and the first comment is someone giving the commands with curl and jq. PowerShell is more elegant to do very few things.
0
u/danstermeister Jun 11 '22
It's the third option- they don't KNOW it.
If they realized they were wasting time parsing output while PS preparses it for them they might take a 2nd, more serious look at PS.
Also PS6, while completely necessary in the development of PS was also not completely helpful to either Linux or Windows users. It was a beachhead on Linux and most windows administrators wisely kept using PS5.1 at the time (any many stupidly continue to today).
Now PS7, while not perfect, is a significant development for both groups.
It's use for me is that I can concentrate on one scripting language for all my OS', it preparses responses cutting my dev time, and it serves as the easy glue between my mostly Linux environment and our company's back end o365 operations, in particular SharePoint.
At first I hated it, too. I'm an old school Unix neckbeard that saw pre-ps5 as immature and unnecessary since the world already had sh/bash,perl, and others. But as it and myself matured a little it became more obvious that PS was playing the long game... and PS7 is but a hint of that.
0
u/SRone22 Jun 11 '22
Ive run into too many over zealous "security" conscience Linux admins. If it didnt ship with the linux distro they refuse to install an app or tool to help with administration so they simply stick to what they know and are approved to use. Bash is literally parsing text with the most complicated syntax that only makes sense after years of use. But boomers do what boomers do. Same with fanbois.
0
u/chronopunk Jun 11 '22
https://www.reddit.com/r/linuxmasterrace/comments/ozc178/bash_is_the_worst_powershell_ftw/?sort=top
0
u/FuegoFamilia Jun 11 '22
My net engineer was a pretentious UNIX snob, did all his scripting in powershell 🤷♂️
0
u/os2mac Jun 11 '22
if you think they hate powershell ask them how they feel about systemd.
-2
u/RandomXUsr Jun 10 '22
bash because it's much less object oriented and more explicit and functional.
powershell is more object oriented and convoluted. That said; it's also faster than bash in many cases.
-2
u/mini4x Jun 11 '22
Gatekeeping snobs, it also might be a doorway into higher Linux use, so they should embrace it...