For me, it's Windows Powershell™.
For me, it's Windows Powershell™
Hunter Gonzalez
Other urls found in this thread:
mathieubuisson.github.io
twitter.com
Jose Williams
tfw still use cd and ls aliases in powershell
Carson King
>Set-Location
Who the fuck actually uses this?
Brayden Campbell
Winbabbies, of course
Aiden Rodriguez
>Set-Location
So this is the power of Pajeet programming
Christopher Flores
imagine writing an essay just to figure out which process is spamming network requests
Brayden Morris
Nobody actually believes Power shell is worth a shit. Right?
Andrew Hill
PowerShell is exactly what normalfags think """"hacking""" is: issuing overcomplicated commands on a black window to get simplistic outputs
Benjamin Jones
It's unironically comfy if you use short aliases for common commands. Using a real query language on actually typed properties is vastly superior to cobbling together some inscrutable sed script + regex patterns in bash.
Colton Thomas
my shell runs an object oriented shell language
Thomas Richardson
lol that bloat
Eli Cooper
Trash shell. I work with it every day.
Logan Garcia
Yeah, why just access the properties I need with a simple syntax, what I need to be doing is parsing text like a fucking caveman?
Ian Sanders
no one, cd is the alias. the formal command is just there for consistency.
Levi Foster
Yeah just memorize millions of objects from billions of different contexts instead of looking for human-readable text
Tyler Ward
Literally the first thing you learn in any Powershell tutorial is Get-Help which is easy as fuck to use, and way better than man. You don't have to memorize any more than bash or the like.
Mason Miller
it is if you are a sysadmin or otherwise work with AD, Azure, Exchange, or Office365 on a daily basis.
Evan Nelson
For me, it's WSL
Xavier Walker
I hope it pays well
Bentley Price
Nobody. It's a great example for why you shouldn't have long case sensitive commands with fucking hypens in them. Fortunately there are aliases.
I think that one of powershell's biggest problems is that Windows blocks unsigned powershell scripts by default. Microsoft basically shot themselves in the foot because now you can't just send a powershell script to someone like you could with a batch script since they won't run by default.
Carter Lewis
Microsoft knows Wintoddlers will blindly run anything they're told to and that would be a huge liability.
Jack Campbell
It does
>you can't just send a powershell script to someone like you could with a batch script since they won't run by default
Except anyone who knows Powershell enough already used Set-ExecutionPolicy Unrestricted
Logan Taylor
What's the difference between setting up sudoers and setting Powershell execution policy once?
Carter Wood
what is padding
Jordan White
People with jobs do (i.e. not you)
Leo King
There's a lot of programs on the internet that come bundled with batch scripts. The same doesn't work as well with powershell scripts.
Brayden Barnes
you dont really use powershell as a sheell to movee around in
its good for doing highlevel windows tasks like editing registries and whatever.
Lucas Miller
Nobody should be setting up sudoers for passwordless privilege escalation and no distro does that
Matthew Murphy
Why the fuck do you have every WSL installed?
Easton Watson
Get a job, loser.
Gabriel Nguyen
Probably so he gets the Linux "experience" - except that his devices actually work.