I would be interested to know when that version was current because that's extremely out of date.
this post was submitted on 24 Dec 2025
381 points (98.7% liked)
Microblog Memes
9935 readers
2736 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 2 years ago
MODERATORS
Don't worry, Microsoft is going to let ai rewrite 1 million LOC from C to Rust per month per programmer and this will dramatically increase the quality https://www.thurrott.com/dev/330980/microsoft-to-replace-all-c-c-code-with-rust-by-2030
Finally, I will memory safe when I accidentally send a broken Invoke-WebRequest 🙂
Windows just isn't ready for the desktop.
Year of the windows desktop is probably not next year; it's not ready for general use yet, it's too broken.
Installing Scoop or Chocolatey isn't much easier either (Powershell permission system) but at least they work and arent stolen from Appget.
Chocolatey was like... Ctrl C, Ctrl V a couple times, and grabbing ChocoGUI. Ezpz
Don't forget the setExecutionPolicy or something.
The cherry on top is the warning about the PowerShell team cooking up their own version of a download command with an incompatible syntax, but still calling it curl.
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.
sent this to a friend, his response:
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.
Yeah lol. Unlike Gates tho, Stallmann actually felt the consequences of his words, and was removed from the FSF. Later he said he had been educated and apologized for his previous statements, he's back at FSF now.
That's why you should use Alpine /s
You mean Alpine GNU/Linux?
Look what they need to mimic a fraction of our power
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.
Trying to install remote desktop multiuser in server manager, for win2025 the installer fails. I find out that a security update broke it over a year ago. Uninstalled all updates then rebooted and it works. Not to mention the constant wack a mole admins do to disable unwanted marketing additions to the taskbar and start menu via group policy and registry hacks. Clearly what windows needs next is an AI powered going dark mode to randomly break features it thinks you don't need. Because even that would be less confusing than what we have now.
Winget is such a half-assed effort. Updating the terminal? Terminal shuts down and you need to open it and run the update again. Updating something else? Maybe it'll change the binary location and not update the path, just for fun (happened twice with LLVM stuff for me). This update failed for some reason? Try to run update again only to be told no updates are available.
Remember when WSL was an actual compatibility layer instead of a VM? Imagine if they had just gone further down that road instead of whatever the fuck this shit is.
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.
Scoop is such an excellent package manager for Windows in my experience. It makes the best of what it's given and it's usually as seamless as using Linux.
All Microsoft developer tools (and that is the target user for Winget) have felt so janky to me. Also, their documentation sucks most of the time.
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 use Choco for system level stuff and Scoop for tools (because it's user level).