Times are a-changin', that's for sure...

It was revealed to me that many much younger folks just store all their stuff directly in the root of their Google Drive/OneDrive/iCloud Drive without folders and just rely on search. This thought stresses me out.

No problem! Hope it gets you to where you need for that task!

Just update the path variables at the start to your relevant paths. This should show you what would be deleted and if you want to do it just remove -WhatIf and re-run it.

```powershell
$flacDir= "/music/flac"
$wmaDir = "/music/wma"

Get-ChildItem $flacDir -Filter *.flac | ForEach-Object {
$wmaFile = Join-Path $wmaDir ($_.BaseName + ".wma")
Remove-Item $wmaFile -ErrorAction SilentlyContinue -WhatIf
}
```

PowerShell is absolutely what I would select for this task! Something like this would probably work (untested, I'm not at a computer right now):

It does indeed work in Windows Terminal. That's my setup at work.

To be clear this is for simple apps or bulk creating apps with a solid baseline. With how varied every product's SAML implementation is, this very likely won't work for many use cases, but I wanted to share anyhow.

YES! Had 3 or 4 expensive can openers. One day the most recent one broke and we picked up an affordable one from the nearest store. Years later it's still super reliable.

Just because something is expensive, doesn't make it good.

That's really cool. I think one I'd the major powers of LLMs is how they're lowering the barrier to entry for learning new skills, and this is a great example of it! Double-edged sword, of course. But this is so cool to hear about. Congrats to her! 🎉

I'm curious to know what you think is so horrible, if you're willing to share!

This is super cool!

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!