You must log in or register to comment.
I’d say Win11 is a joke but its more like a slap in the face.
And a joke…Its still a joke…
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 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.
Microsoft won’t fix it either because they’re too busy adding AI features to every part of the operating system.
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 🙂
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.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.
Microsoft just set a system wide default alias in Powershell for
Invoke-WebRequestcalledcurl.While I get their reasoning for that (I mean, they also aliased e.g.
lsanddirtoGet-ChildItemwhich 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.-Forcemay be abbreviated-fas long it’s the only argument starting with f. Whiledirorlsis somewhat likely to be called without arguments (or maybe -f) that’s definitely not the case forcurl.wait they’re fucking with the dir command? wheres my torch
Yes. Somewhat. In Powershell
diris an alias forGet-ChildItem.While
dir .ordir C:\test\works as expected, you could also do this:dir HKLM:\HARDWARE -Recurse -Depth 5which will list your registry from the local machine from the keyHARDWARErecursively - but only to a depth of 5 levels.
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.)
Ansible, the declarative configuration manager
Ansible declarative? That takes a lot of effort I think.
Hm? Most of the time the config is like ‘these packages should be installed, and these files should be in these directories’. Even stuff that requires running shell commands can and should be written in an idempotent way, basically just checking if the changes are already done.
Though Ansible kept introducing features like loops and conditionals, but the latter are required for aforementioned checks, and loops are useful for sanity. I’m more irked that they basically reinvented Lisp again, but with an inconvenient syntax.
I was talking about playbooks mostly, not individual tasks.
E.g. if you have a playbook where in one location you make sure a package is installed and in another to add a line to its config files, you need to ensure installation is performed first.
Another generic example is conflicting definitions, e.g. you define a package as present and somewhere else you define that one of its dependencies should be absent. Depending on the order, you either get an error or it works fine (but ignores the package absent directive). Or is my understanding wrong here?
You make me think of a Doctor Who novel.
I would be interested to know when that version was current because that’s extremely out of date.
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.
It is truly unfortunate so many figures people foolishly look up to are just secretly (or not so secretly any more) comically evil.
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.
Bruh, hes pro child rape.
He was friends with epstein.
You can’t just apologize and undo things like that.
It is a travesty he continues to be a part of that organization considering the no code/subtraction he contributes,
I bet there are a lot of donations they could be getting but aren’t purely because of this, and the fact that he clearly had some sort of leverage on them to be able to be reinstated.
That’s why you should use Alpine /s
You mean Alpine GNU/Linux?
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.
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.
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.
Textbook Microsoft move. Thanks for the link, that was an interesting, if disgusting, read. I loved in particular that they were difficult about reimbursing his travel. You’d think a multi billion dollar company would be able to pay for however much a plane ticket and possibly a hotel stay was…
That’s not the first time I hear something like that from a big company. I saw a talk by Matt Godbolt (compiler explorer) mentioning that NVidia took more than a year to pay him some contribution they said they would for the CUDA support. Can’t remember the figure, but it was ridiculously low.
<sarcasm>
Keep faith in Microsoft, they are planning a massive rewrite of 30+ years of backward compatible code in Rust. Will save us all…
</sarcasm>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.
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.
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.
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).
