You can test the load speed without loading a profile:
```powershell
Start-Process powershell.exe -ArgumentList "-NoProfile"
```

I spun up both Windows PS & PS 7 w/o any profiles & they launched in 243ms/162ms respectively, which I think is reasonable for my shell to load into a terminal emulator.

Launching PS takes longer than others, because PS is based on .NET, so runtime needs spun up for that session, modules & assemblies loaded etc.:
1. Process created
2. Common Language Runtime loading
3. Engine init
4. Load your profile (the part you posted about)

That seems long for sure! My profile is loaded with a bunch of custom stuff and still takes less than 2 seconds to load...

You can check the contents of your profile:
```powershell
Get-Content -Path $profile
```

Or if you want to open it in Notepad...
```powershell
notepad.exe $profile
```

It was something for an eclectic casino system. I don't recall what exactly was going to cause it to break but I remember debating for a bit before deciding it was very much a non-issue.

Hope the rest of your conversions go okay. Lots of reference material for PS out there and lots of good and knowledgeable folks in the community willing to help those seeking it!

Ah, my condolences. If they want to use different tools so badly maybe they should help convert/maintain the scripts 😉 That's neat that you're willing to convert them so they can use what they want, though!

If you already have perfectly working bash scripts, why reinvent the wheel? I'm genuinely curious -- not a criticism. Nothing wrong with using bash where it makes sense, especially if you already have a well-built and functional arsenal of scripts!

You certainly don't have to like it; many don't.

But I don't think it is broken.

I'd also note that while a variety of languages have used `mkdir -p`, not all of them have. The ones that have are usually stemming from Unix systems of yore. There are lots of languages out there, not all of which are based on Linux shell scripting. PowerShell is built on .NET.

But is it broken if it was intentionally done that way, and is working?

To be fair, we knew this was coming. But still.

No problem.

`Get-Command *searchTerm*` helps you find commands if you don't know the cmdlet names.

`Get-Help commandName -Full` is like `man` from *nix-land and is great for figuring out how to use cmdlets.

That and the community is very helpful if you have future issues! 😁

I suppose I was incorrect to a small degree: the `-p` argument if you're coming from *nix-land won't behave the same way in PS on Windows. It would be interpreted as the `-Path` parameter, so in this case you'd want `mkdir uuu -f` so it interprets `-f` as `-Force`. My apologies!

So the directory "uuu" already exists in your present working directory? (You can confirm if this is true using `gci` which is the alias for `Get-ChildItem`.

may i offer you some corgis in these trying times

It definitely can be at first! The ease comes with time and experience, as it does in pretty much any language.

Fun fact, all these do the same in PowerShell!

```powershell
# cmd style
mkdir -p output

# PowerShell using alias
ni output -it d

# PowerShell full cmdlet
New-Item -Name "output" -ItemType Directory
```

One of the objectives behind the verbosity is that it is extremely human-readable.

This is my favorite thread I've seen today 😂 I've soooo been there