Use case?
>>109689033sysadmins on old machines to feel important and cool
Creating a moat for Microsoft.
>>109689033I seriously believe this is the worst piece of technology ever created.
>>109689033>Use case?Solving captchas with simply pasting a command
running remote scripts
>>109689033Oh fuck, I see the merchant!
shellGoogle it next time.
>>109689118holy shit
>>109689118Ultimate nooticer
>>109689033It powers hell
>>109689118The Master Race is everywhere.
Windows Infosec
>>109689033>.NET Core>Scriptable>Can manage everything. WMI, Registry, Filesystem>ExtensibleMogs everything else.
>>109689033Powershell commands make a lot more sense than freetard ones. Compare Get-PhysicalDisk and lsblk. Get-Disk/Get-PhysicalDisk is clear as day. lsblk is obscure. First you need to decipher that "blk" refers to "block storage", a term that no one uses in the real world. The lsblk drives themselves are listed as "sda", "sdb", which is another nonsense acronym a user needs to decipher for no legitimate reason. It's abundantly clear which one was designed by white people and which one wasn't.
>>109689033I'm not working as a sysad anymore, but when this got released it was better than vbscript. If all powershell ever did is replace vbscript, it did gods work in my opinion.
>>109689033>Use case?power users don't need a use case. they need power. because they are power users.
>>109689033>Use case?Merchant Shell. Can't unsee
>>109689066I wholeheartedly agree with you
>>109689192Lol, you don't have to use it, like me
>>109689397POWER
>>109689033Activating windows
>>109689033>Use case?to ssh into my dev box
>>109689033Yelling at chat gpt to fix some shit while copy pasting commands and output like a good little meat proxy
>>109689033Great for dealing with Windows based systems. You'll never use this outside of work.Pretty good for managing the Active Directory
>>109689033>Use case?winget upgrade --all
I like to open the powershell just to get the Windows machine spirit hopeful before I type 'wsl' and ssh onto the container where I do real work.
>>109689033>Out-GridView
>>109689201Decent bait. 6/10. Your major point of failure is here:>First you need to decipher>a user needs to decipherOne need not decipher anything to type or paste any command. No shell forces you to write an explanation of the command prior to execution.
Takes a fat dump on both Batch and Bash, and object-based functions and scripting are actually genius once you wrap your head around it and mog the 70's Bell Labs "just grep and regex everything" caveman mentality.Of course, if you're a freetard, you'll never admit it. You'll just screech about EE&E and preach your outdated ways as "superior" simply because they come from your cult.
>>109689118I hate when someone is a better racist than me.
>>109691385You sound triggered.
thumbnails exiftool
>>109689033malware dropper
>>109691416Better to ignore that anon. Resident anti-Unix / Unix-like OS spammer. Will incessantly shit up the thread if you trigger her enough.
primarily for making me have to type 'cmd' into the terminal that opens from the shift+right click context menu so i can actually do shit like a normal person
>>109689033Automating any task on Windows that you could do via the GUI
>>109690334And scoop update *
>>109689201Sure but after the first n times you don't need the full descriptor anymore and it just ends up being verbose to type everytime. Autocomplete also isn't great on powershell as there are a bajillion options and it will never complete to the one you want until you type like 90% of the command.>>109691385Shell scripting does not need to be powerful. Just quick, concise, and easy to prototype with as you go. As soon as you need anything more complex you should write a proper program whether using a compiled language or a scripting language. Not saying bash or even posix are great(they can be very very obtuse at times), but they're more useful than powershell for shell usage due to how easy it is to try things out.
>>109689033i fucking loath windows, and usually have a mingw install to make it tolerable, but if i have to use a native shell, at least powershell isn't cmd.exe
it's good if you're stuck in the microsoft ecosystem. i mainly use it for active directory stuff since it interfaces really easily
>>109693939This. Many of us are stuck supporting windows crap ar work.
>>109689033No use case since by default you can't run unsigned scripts. And when someone tries to allow execution of unsigned scripts wintards start screeching about security risk lmao.
>>109689033>Use case?Automations and configuration on Windows.It's the shell that makes the most sense in modern Windows which it's interfaces provide structured data.https://en.wikipedia.org/wiki/PowerShellYou can read the wiki and brief yourself a bit on the "why?" part.
type winget upgrade --all from time to time to emulate Arch Linux experience
Batching windows tasks, neat for troubleshooting user workspaces, saves a lot of time resetting someones user profile if you start up a batch input a username and everything is done for youCan be done in other programs sure but those often arent made by agents, powershell is lowbar that servicedesk agents can easily whip up a batch to make their own work more efficient and easierFor actual admin shit just use normal admin tools
>>109689118kek,
>>109689560Unlimited
>>109689118>_
