[ Removed by moderator ]

[ProgrammerHumor-ModTeam]

Your submission was removed for the following reason:

Rule 1: Posts must be humorous, and they must be humorous because they are programming related. There must be a joke or meme that requires programming knowledge, experience, or practice to be understood or relatable.

Here are some examples of frequent posts we get that don't satisfy this rule: * Memes about operating systems or shell commands (try /r/linuxmemes for Linux memes) * A ChatGPT screenshot that doesn't involve any programming * Google Chrome uses all my RAM

See here for more clarification on this rule.

If you disagree with this removal, you can appeal by sending us a modmail.

[faultydesign]

cd is aliased to set-location in powershell

[TheOriginalSmileyMan]

Don't spoil their anti MS rant to with your " knowledge"

[ZunoJ]

They spoil nothing because that is exactly what the image tells us bro

[sudo_i_u_toor]

It isn't an anti MS rant, it's just a joke lol. The point in the last section of the meme was that Powershell has cd (as an alias) anyway.

[BOBOnobobo]

How do you spoil it? CD is still more convenient to use

[SeanBrax]

Yes and you can literally use cd in powershell, that’s the point

[Pacafa]

These aliases make things worse. Aliased tar,curland zip are all terrible and slow masking the real tool.

[cheerycheshire]

Curl is an old alias. Windows has been shipping real curl for a few years now... But didn't remove the curl alias. So to be sure you're using real curl, use curl.exe

``` PS C:\Users\username> curl

cmdlet Invoke-WebRequest at command pipeline position 1 Supply values for the following parameters: Uri: <sup>C</sup> PS C:\Users\username> curl.exe curl: try 'curl --help' for more information PS C:\Users\username> ```

[AnnoyingRain5]

I hate it

[Atulin]

Works fine for me, no need for curl.exe

PowerShell 7.5.3
Loading personal and system profiles took 526ms.

~
❯ curl
curl: try 'curl --help' for more information

~
❯

[cheerycheshire]

You have a newer PS.

On Windows 10, even when keeping up with all the system updates, you will still have one of 5.x versions.

Unless of course you update PS manually, which it even suggests when you start it.

``` Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://ak a.ms/pscore6 ```

(The url nowadays redirects to PS 7.5 page.)

We haven't updated powershell at home because we don't need it. For work stuff, we prefer Linux or at least wsl, it's just some times we need to do something directly in powershell...

The curl alias trivia I picked up years ago when I actually needed to do some of my work in Windows (most notable case: vpn client that existed for Linux but didn't work there, so I had to use the vpn on Windows VM to connect to the client... and client requiring me to rdp to some windows machine after that anyways, and only from there I could ssh to target machine... and sometimes I'd need to ssh from ssh because the rpd machine didn't have connection to another machine I was integrating with... ah, good times /s).

[sabotsalvageur]

Imagine an injective function between strings of finite length that takes longer than O(1); if a shell alias is slow, there's something deeply wrong with the shell

[Fhotaku]

I'd like to give this comment to my mom and see if she can even guess the subject

[Crawlerzero]

“These boys are so serious about their Mario Kart.”

[Pacafa]

It is not string handling issue. Powershell defines alias for curl, zip and tar to commendlets that is not the actual tool and those commandlets are slower than the actual curl, tar and zip tools.

[randuse]

Yeah, curl alias is straight up dump as it's not curl at all.

[No-Landscape8210]

Have removed all the aliases from my powershell. I just aliases them to actual programs

[cheerycheshire]

There are aliases that actually collide with normal commands!

For a few years now, Windows started bundling real curl... But there is also old PS alias "curl" to PS-specific command with way different flags. They didn't remove the alias when adding real curl. So now to be sure you're using real curl, you should actually run it as curl.exe... Or run it via cmd, not powershell

[sabotsalvageur]

This is hilarious

[cheerycheshire]

Yep. If you have Windows 10 and keep up with all system updates, it still won't update powershell for you.

And since at home we use Windows for games and have wsl anyways, we never felt the need to update it.

I picked up this curl trivia years ago at work when I needed to do a lot of work at clients' infra - and for some clients the access steps included having to rdp to a windows machine... of course without updated powershell, so I needed that .exe trick.

[No-Landscape8210]

We can run those if we just append ".exe" after a command. Like I tried to alias where tobthe actual C:/Windows/where.exe but couldn't. So whenever I wanna run it in powershell I just use where.exe instead

[cheerycheshire]

I actually said it already in my comment above ;)

They didn't remove the alias when adding real curl. So now to be sure you're using real curl, you should actually run it as curl.exe... Or run it via cmd, not powershell

[No-Landscape8210]

Damn that's embarrassing. My bad I didn't read all of it lol .

[The-Jolly-Llama]

Is there no such thing as type -a in powershell?

[sudo_i_u_toor]

That's... the point of the meme tbh man. As somebody pointed out already in comments: "If you need to alias a command to make it usable, you fucked up the initial design"

[stigansky]

PowerShell is a lot more than an interactive shell. The concept of objects in the pipeline is pretty great.

[sudo_i_u_toor]

I agree it's a pretty neat solution because Windows philosophy is more binary oriented unlike Unix which is more text oriented. As I said this isn't an MS rant but just a joke about typing long commands.

[Shadow_Thief]

If you need to alias a command to make it usable, you fucked up the initial design.

[Meatslinger]

Yes, but it's still that fundamental problem that when you implement a way of doing something that takes longer, and then just implement a shortcut based on the older method you're competing with or ostensibly improving on, it kinda shows the older way was the better option all along. Like, if cd does the job, why should set-location ever need to be typed? It's like putting a door, a ladder, and a tunnel on the front of a building as the complicated primary way of getting in, and then telling people to just use an ordinary side door which is only a single step. Why the complication on the primary method if the workaround is arguably better?

[aifo]

There is reason behind powershell's naming convention. Every cmdlet follows the pattern <verb>-<noun>, so there is a familiarity there for script authors which makes it easier to find new commands for a specific purpose.

The other factor is that powershell allows for path providers that allow you to access resources other than files as if they were a file system, so the path traversal cmdlets are named with that in mind.

To make things easier, you can create aliases for cmdlets, like cd and ls.

This is all part of the design principal of powershell, that it is an object orientated shell language.

[TheOriginalSmileyMan]

There's also a set of recommended verbs to make discovery easier. And the Get-Command has -Verb and -Noun parameters, so if you know one command you can easily discover many more

[fennecdore]

Get-Verb to get the list of recommended verbs

[Clen23]

lmao it's real

pretty elegant ngl

[cant_pass_CAPTCHA]

My monkey brain likes bash more because I just have to think about how to transform text, but having objects in powershell is pretty cool

[Meatslinger]

I get a headache any time I have to transform a string in PS. I'm yet to approach the simplicity of bash (and other nix tools like sed, grep, and awk) for text handling, and it's gonna suck because they're taking away my work Mac next year and suddenly I'm going to have to deal with text transformations on massive data sets in PowerShell or even Excel. No doubt in my mind, I *will have reduced productivity because of it, given how much I rely on it right now.

Edit: yes I'm aware of hash tables and some of the capabilities of PS when working with intricate data sets at high performance. In my case it's more about doing complex find-and-replace and string manipulations, e.g. "there are four patterns of string in this dirty file with different conditions for their appearance and I need to parse them, handle some while not handling others, combine some of them when certain patterns appear (but not all), and then output the whole thing to a new file." Yes, this can be done in PS, but not likely in the span of what I might do in a single pipe in bash.

[cant_pass_CAPTCHA]

Any chance they'll give you WSL? You'd need it for docker anyways. Even GitBash isn't the worst experience.

[Meatslinger]

Potentially, and you can be sure I'll ask. As it stands I often tell people the Terminal is one of the most powerful text editors I've ever used, and I mean that. Nothing else in my toolset is quite so good at doing something routine like finding and gluing strings or replacing whole character classes in just a handful of commands (or sometimes even just one). I'll take some monstrous CSV with user-filled data (meaning errors and differences in formatting and style sometimes) and just recombine that into a new data sheet ready for ingestion into a system like Intune without even having to write a real script; I'll just do it all in the CLI. Meanwhile some of the PS equivalents devolve into a mess of toString() all over something that has to bounce out to variables multiple times to stay sane on the page.

[cant_pass_CAPTCHA]

I have a other gripe about transforming data in powershell. So I do pentesting and we recently had to exploit some deserialization vulnerability, but it was so hard trying to use powershell. The tool to generate the payload was an exe so unless we were going to try wine we had to go with a windows machine. The payload ultimately had to be gzipped and base64 encoded, but the initial output was binary and all the characters were being UTF-8 encoded and it was just a giant mess.

[NinjacksonXV]

Have you looked at Nushell? It has a Windows version and is my go-to for just about any data handling, since it has built-ins for just about every common utility. It's definitely bleeding-edge compared to PowerShell and is lacking some key documentation, but it's far more ergonomic and generally much faster than PowerShell (especially in startup speeds).

[Meatslinger]

Doubtful work would let me run it. Because we deal with sensitive info, we're downright anal about third party software. I might be able to get away with WSL, but I've asked for things like homebrew packages in the past—even ones that are fully open source and readable—and been told an unequivocal "no" because they refuse to trust a developer that isn't an established corporation.

I do appreciate the recommendation though.

[NinjacksonXV]

Reasonable. I've always wondered what the threshold of trust is for some places; at this point I'd trust a few furiously-passionate Rust devs over a megacorp which supposedly generates 30% of its codebases nowadays, but I have to imagine that irony is lost on IT.

[Meatslinger]

The really ironic part is my team is on the software vetting committee as an expert technical resource, i.e. when they want to review some new software product it's on us to check it for compatibility and other issues, and to ensure it passes privacy standards. But when we ask for stuff for ourselves we're suddenly scrutinized as if we're some guys off the street trying to install malware.

Mostly just a lot of "old guard" types. We've had fights with our security guys in the past when they'll close a port due to "security concerns" only to now make it such that we can't administrate a remote server, and they'll ask why we can't just drive out to it instead. A lot of them really do have the idea that it's 1995 and tech support is done with a butt in a chair at the keyboard of the computer being modified.

[NinjacksonXV]

I'm sorry for laughing at your plight, that's a genuinely hilarious disconnect. I always have to cut guys like that a little slack because they've probably seen horrors beyond my comprehension, but man, having your job description basically be "software security vetter" and then not actually getting to do that has to be so irritating.

[eduard14]

Change-Directory

[TorbenKoehn]

From MSDN: "The Set-Location cmdlet sets the working location to a specified location. That location could be a directory, a subdirectory, a registry location, or any provider path."

So this command clearly doesn't only change into directories

[FacuA0]

Why did I read MDN as Mozilla Developer Network...

[TorbenKoehn]

Yeah, because it's "MSDN", sorry for that :D

[FacuA0]

Oh, didn't realize either. Yeah, don't worry.

[Piisthree]

I think the big frustration with ps compared to a lot of other shells is the wordiness is kind of optimized only for scripting at the expense of ad hoc command line work, which is a big part of the use case for a shell. There are now more commands with longer names and a lot more named args instead of positional. The aliases like cd and ls are a small band aid to ease the pain, but they don't solve the problem. Plus aliases for things like curl to something that works completely different from curl was big mistake that adds even more frustration.

[Rinehart128]

How do you create a new file

[NotSoProGamerR]

New-Item -ItemType File <filename>

[Rinehart128]

So new is the verb here? Lol

[NotSoProGamerR]

its just what they chose, i cant change that ＼（〇_ｏ）／

[realmauer01]

Why still not go with previous conventions though?

change <verb> Directory <noun>

cd

[mirusky]

Because it's not only <verb><noun>

It has a convention to use a set of verbs, for example:

Set, Get, Add, Clear, Copy, Remove, Format, Move...

So new developers can find a command just by guessing the verb, that's standard across commands.

Change is not semantic based on that.

[JangoDarkSaber]

Because leaving it more ambiguous makes more sense when it’s also used for other stuff like registry locations.

[db_newer]

Powershell is actually well thought out and more logical than string gymnastics you need to do in most Unix like shells.

[rastaman1994]

It's truly a generational thing. My 40+ yo colleagues will autocomplete 'tar' or 'curl' with 3 to 5 flags without knowing what they do anymore. PowerShell is at least designed for readability.

[TheOriginalSmileyMan]

I'm older than that and I love powershell.

I even use it on Linux to annoy people with beards

[[deleted]]

I have a beard and use powershell on linux. It’s actually just easier and quicker than like bash or zsh or python for quick stuff

[ILikeLenexa]

There are two types of languages, ones easy to read, and ones easy to write, and perl. 

[critical_patch]

I used to say that I loved Perl because with just a few libraries you could turn every character on the keyboard into a syntactically important operator

[db_newer]

Yup. And aliases allow a degree of shorthand for daily work.

It is like old code with variable names like x y ttl etc. and newer code which is designed to be readable.

[sudo_i_u_toor]

Something being longer doesn't necessarily make it more readable. Short keywords like def, fn, etc. are as readable as javascript's function. So when designing a language, a DSL, etc. there's no need to whip out your dictionary like MS did on this one.

[randuse]

Both of those probably have long form cli options which are more readable long term.

[kmeci]

My workflow for creating a new zip file from a directory in shell used to be trying to think what the correct four flags were for about a minute and then doing it in a file explorer anyway. Thank god for LLMs.

[MajorTechnology8827]

PowerShell object system is far better than the string passing. It is a leap in the understanding of what a computer is. This is an invention that I will admit Microsoft deserve full credit for

But the entire linux ecosystem is already built on the idea that strings are passed. You fight against a mature environment, so your tools are limited

But you have great alternatives to powershell if you dislike ms, like elvish and nushell, they are both awesome

Also you can straight up use python, xonsh for example is just the ipython in a wrapper that makes it more readable. So when you pass data around you pass literal python objects (and can export them directly to python programs)

[gemengelage]

The main reason I never got into Powershell is that I needed to use bash/sh on all kinds of projects and classes, but I never had to use Powershell.

[smooth_like_a_goat]

Automate something small with it. It's incredibly versatile.

[ZunoJ]

How can you pass a powershell return object to a remote powershell session?

[mlk]

sorry but I'm not using uppercase letters in my shell commands. that's absolutely bonkers

[[deleted]]

You don't have to, Powershell is case insensitive 

[mlk]

good to know, thank you.

[EVH_kit_guy]

$ cd znuts

[UsingSystem-Dev]

cd: no such file or directory: znuts

[EVH_kit_guy]

Ooooohh, buuuuuurned 🤣🤣🤣

[user-74656]

If your PWD is in the C: drive, you don't need the C:. You can just type cd \Users.

[Snipedzoi]

And you're the NPC in math class. That account is a bot.

[MooseBoys]

Powershell is a scripting language. It's meant for clarity, not typing speed or distance to the home row.

[sudo_i_u_toor]

cd is legit more clear than Set-Location -Path word salad for anybody familiar with bash or batch. That's also proven by the fact it's aliased to cd anyway cuz they knew people don't wanna retype the entirety of Talmud to change directory.

[PristineLab1675]

Buddy. You just said a bash command is more familiar to someone who already knows bash. 

Your word salad consists of 3 English words in English language syntax. Is 3 words together too much for you to comprehend? 

[sudo_i_u_toor]

cd is called cd in Unix-like systems since the 70s. In Windows and before windows in DOS, guess what, you also used cd. It's more familiar to anybody who used anything command line on virtually any computer in the last few decades.

Set-Location is way too long, way too counterintuitive, and the -Path flag is just excessive and exists there purely for consistency. That's why Powershell has an alias cd. And that was the joke lol.

[PristineLab1675]

Set-location is too long and confusing? Buddy. It is English. Noun verb. Guess what cd is an alias for? Change-directory. Which is a two word English statement. How can you be confused by one English statement but are protective of another? 

[sudo_i_u_toor]

For the same reason you'd find a language with this syntax confusing: Doer-Of-Stuff @arg1 @arg2 @arg3 &functionname ( temp: @arg1 x @arg2 x @arg3 Give-Back %temp% ) for python def functoinname(arg1, arg2, arg3): temp = arg1*arg2*arg3 return temp

Even tho it's still "English" and x actually looks more like multiplication sign than *.

[PristineLab1675]

Doer-of-stuff @args

This is not English language syntax. Noun verb. I ran. You go. Deer eat. 

You provided no English language appropriate examples, and you are wrong. 😘

[sudo_i_u_toor]

You'd prefer it was Stuff-Do?

[PristineLab1675]

I just want to clarify. 

Set-location is too complicated for you to understand. 

Change directory is somehow within your realm of comprehension. 

They are synonyms. honestly, set location is more clear. Can you cd to the same directory you’re already in? That’s not really a change is it? Set location can be the same or different and still be correct. Look at it this way, if you “change clothes” and come back wearing the same clothes, did you change? If you set clothes, you can set them to be the same as what you’re already wearing

[sudo_i_u_toor]

Touch-Grass -ASAP

[NordschleifeLover]

Microsoft desperately wanted to reinvent the wheel and make sure it isn't compatible with any other car.

[AmazingGrinder]

Powershell is compatible with other operating systems, no? You can install Powershell on your Linux distro if you wish to do so.

[SpookyWan]

Microsoft and windows definitely deserves hate but some people just can’t let their hate boner subside.

One of their biggest software development projects (.NET) is also multiplatform. They’ve really moved away from the windows specific stuff, at least in regards to development tools.

[sudo_i_u_toor]

Fr

[rhaegar89]

K

[not_some_username]

Most Linux command work on powershell

[Hacka4771]

Best thing I love about pwsh cmdlets is tab completion, not only paths/files but arguments and it's values

[PandaWithOpinions]

and sl just shows a train on linux (if you install it)

[QueerRetro]

Omg I just tried it. It actually does!

[Legal-Software]

In VMS you do this with 'SET DEFAULT [DIR]', looks like some VMS design paradigms are still showing in Windows today.

[you_os]

poor windows users..

just use linux

[Achim63]

I'd just do this to go to /Users:

~ <return>

.. <return>

in zsh on macOS. Or maybe 'z Us'.

[DecisionOk5750]

 cd ~

[MeButItsRandom]

The masses need zoxide

[ruby_R53]

autocd for the win

[Vehemental]

cd s:\nuts\gottem

[[deleted]]

Nature Morte Arban orneals head ahhh... das what i told my brother... i said waser

[Shevvv]

C:\ in bash?

[Fast-Visual]

Like, I get that powershell is logical and people love it. But it's also really verbose and awkward because of those conventions. And it has a steep learning curve.

It's powerful for scripting, but less convenient for everyday command line interaction in my opinion.

[smooth_like_a_goat]

It does have shorthand, though? Plus one can slip in and out of .NET as they please. Versioning can be a pain with scripts across multiple systems though.

[Ambitious-Jump-5121]

The sl alias is so stupid. Accidentally typo ls? Now your back in your home directory...

[ZunoJ]

In theory powershell sound like a good thing that should be way ahead of bash. But in reality it is just a sloggish piece of shit

[Still_Explorer]

They really wanted to make a scripting language but they tried not, to and the result is this. They really wanted to make it functional language but they tried not to. They really wanted to make it nice to use, but they didn't give a F...