*IN* the operating system? No thanks. As a third party tool that I can optionally interface with? Sure!

E.g. if I want an LLM I'll run Ollama in a container, install Gemini CLI, etc.

But I do not want AI baked into my operating system.

For perspective, I enjoyed Links Awakening much more than BotW. Maybe thats a hot take. But that's just how I felt when playing both games.

That said, not even game (or product for that matter) is made for every person. If I just wasn't the target customer/player for BotW, then I'm okay with that even if it makes me a little sad.

My issues with BotW were that it was like they tried to make it graphically pretty, and missed the mark a bit for me and that the open world was massive but felt relatively empty and spread out. There was a lot of world building/environmental cohesion missing for me.

Every time I accidentally do this in Discord, I'm immediately angered.

If you miss it, PowerShell 7 is cross-platform and available on Linux, macOS, and Windows 😄

Objects are cool.

Fully agreed! Absolutely love their stuff.

```powershell
Get-FileHash -Path "C:\path\to\file" -Algorithm SHA256
```

Or I think in the GUI if you right-click the file and go to the Details tab you can view it there, but I can't remember if that's completely accurate.

MicroITX build in a Fractal Terra case with an AMD Ryzen 7 5700X, AMD Radeon RX 7800 XT, 64 GB RAM, and a few TB of NVMe SSD storage.

And the PlayStation 5 runs Orbis OS, based on FreeBSD not Linux 😉 though a PlayStation running something other than Orbis OS is definitely a cool thought.

Got a machine for that too 😁

Isn't it great how anyone just do basically whatever they want with their computers?

Pretty cool timeline we live in.

That's amazing. It was my go-to when I first got into learning PowerShell, but once I found VS Code there kinda wasn't any going back for me unfortunately. Shame it didn't get more attention. I could see a world where it got continued love and came out as the en vogue scripting application.

True! I did my testing in a Windows PowerShell 5.1 profile in Windows Terminal. I didn't even think of testing in ISE to be honest. Haven't touched it much since moving to VS Code years ago.

To be clear, I don't actually know what Expand-Archive is doing internally. I'm just assuming (very possibly incorrectly) what is happening. It looks like Expand-Archive hands off the extraction to a private function ExpandArchiveHelper. Maybe someone who isn't me knows what happens in that function

Some of us are running PowerShell on our Linux machines. There are dozens of us!

While you could theoretically disable real-time scanning during the extraction, I wouldn't recommend it. Someone more knowledgeable than I probably has some more fancy tricks to improve performance as well.

So if you're programmatically expanding archives, I'd definitely include commands to temporarily change your $ProgressPreference and change it back after the expansion for a fairly impressive performance gain!

Finally, I tried calling .NET directly:
```powershell
[System.IO.Compression.ZipFile]::ExtractToDirectory($path, $destPath)
```

This took 22s, which was another slight improvement.

Next, the same command but temporarily disabling the live progress bar:
```powershell
$progressPreference = 'SilentlyContinue'
Expand-Archive -Path $path -DestinationPath $destPath
$progressPreference = 'Continue'
```

This took around 25s -- much faster! This is where the bulk of time is wasted.

First, just regular.
```powershell
Expand-Archive -Path $path -DestinationPath $destPath
```
It took around 1m 8s.