Funny thing: judging by the styling, that text might be from the documentation for Ansible, the declarative configuration manager. Well, you can't run Ansible itself in Windows, you need a *nix vm, even if WSL — though you can control Windows machines via Ansible. Afaik the same is true for the popular alternatives Salt, Puppet and Chef.

(Though I couldn't find the screenshotted page.)

You make me think of a Doctor Who novel.

Microsoft just set a system wide default alias in Powershell for Invoke-WebRequest called curl.

While I get their reasoning for that (I mean, they also aliased e.g. ls and dir to Get-ChildItem which is the same, but way more powerful than the OG commands the aliases hint at), the problem is, that in all those cases the arguments don't match. Something that plays in the favor of Powershell is that arguments are not case sensitive and do not need to be written in full, as long as they're distinct - e.g. -Force may be abbreviated -f as long it's the only argument starting with f. While dir or ls is somewhat likely to be called without arguments (or maybe -f) that's definitely not the case for curl.

They don't do that anymore in new versions, but you still need to actually use the new version to get that behaviour. It's a bit of a pain since the "fixed" version is in the MS store, the broken one is a base system component.

It also hits the people who use the terminal the least, anybody who uses it regularly will just install the new shell at the same time they install the new terminal and always get the new clean behaviour.

Year of the windows desktop is probably not next year; it's not ready for general use yet, it's too broken.

Glad he went with Terry Davis and not Richard Stallman.

Note: This is posted in the same tongue in cheek manner as your image and not meant to conflate Bill Gates and Richard Stallman.

Finally, I will memory safe when I accidentally send a broken Invoke-WebRequest 🙂

You want even more shame here? They made Winget by basically copy/pasting a solo dev effort called Appget back in 2019 after stringing the dev along about a possible Microsoft job.

Then, during the annoucement of winget while they lauded other windows package managers, they barely mentiom his app they copied nearly 1 for 1.

Afaik original WSL suffered from the fact that filesystem syscalls went through Windows' APIs, which allow user-level third-party programs to plug in at many points — like path resolution, block access, etc. Which also involves switching the context between the kernel and userspace a bunch of times. File access patterns in Linux apps worked poorly with this. Plus Linux apps expect the filesystem to cache metadata, which Windows doesn't seem to do.

Much of this is mitigated when file access on the Windows side is done by chucking blocks into and out of a virtual disk, and when a kernel with the whole caching thing is introduced.

I'm guessing such mismatch problems would crop up in other places too.

I use Chocolatey, but I've looked at Scoop before. Any big differences between the two? I just don't want to relearn commands and edit scripts (for multiple machines, and scheduled tasks) if I get the same outcome...

i was forced to switch to Win11 and after three weeks my employer straight up apologized and allowed to switch work computer to Mint. And then much of the team also switched to Mint and it turns out your computer can still feel like the machine from the future when its OS is not a bloated spying mountain of crap

Windows 11 is vibe-coded garbage. Vista was a better OS at launch than 11 is 4 years in.

Chocolatey was like... Ctrl C, Ctrl V a couple times, and grabbing ChocoGUI. Ezpz

i used to prefer MIT and Apache licensing. now i feel very strongly that copyleft is the way. too many rugpulls all at once in the last 2 years.

From what I've seen people say not to install server 2025 at all, due to a bunch of unresolved issues. I'm suspecting that 2022 will be the best for a while.