I think it's more likely that Microsoft is vibe coding slop garbage to replace their core apps that were literally better.
Windows 10 explorer.exe is 100x faster than Windows 11 explorer, it's not even close.
It also signals the death knell for Windows native apps. Microsoft can't make them anymore. It won't be long until even Excel is a Electron sloplication.
> Windows 10 explorer.exe is 100x faster than Windows 11 explorer, it's not even close.
I have a hard time believing this. I'm pretty sensitive to performance losses and I haven't noticed any difference between those. It wouldn't make sense either, given they should both host the same shell icon views. Are you sure the difference you're seeing is in explorer.exe? As opposed to something else, like a new shell extension or a new filesystem filter driver on Windows 11?
It is certainly perceptibly slow. Carried out a test on my 12 year old PC running Win-10 vs a new HP Win11 laptop of my friend which he bought in a hurry before price increases. Opened a directory of several thousand files with nested folders - much slower at navigation. Much slower at opening right-click menus. Much slower at pretty much everything.
M$ has now introduced web-latency into the desktop along with their adoption of web-tech into the OS. You gotta get used to staring at that spinning blue circle, counting the many precious moments of your life draining away.
You could at least disable Active Desktop to dethrottle your PC. Meanwhile, my work W11 PC has a second+ delay for explorer right click and there's nothing I can do about it.
You can actually restore the old right-click menu on W11 with some regedit.
Not ideal in any way, and a setting would have been a much better way to toggle this, but it is an option.
I've found that ( at least for me ) that was caused by some entries doing some checks before showing up. Getting a context menu editor and removing some of them can help.
Doesn't matter, it's a shit user experience and Microsoft's fault for putting the onus on the user to fiddle around at that level, rather than putting a hard, very low limit on how long shell extensions can hold up the context menu before they're banned from it.
Oh, I'm not trying to defend Microsoft in any way. Everything they make has been going downhill faster and faster.
Just suggesting a possible way to work around it.
> rather than putting a hard, very low limit on how long shell extensions can hold up the context menu before they're banned from it.
Do you want the users to blame Microsoft, all Microsoft employees including catering and cleaning workers, and Gates personally? This is how you make the users blame all the before mentioned but not the culprit.
> As opposed to something else, like a new shell extension or a new filesystem filter driver on Windows 11?
Ultimately, what difference does it make? The file explorer in Windows 10 is much faster than the one in Windows 11, and it's very noticeable. Turn on the old context menus, and try right clicking a file. Instant in Windows 10, visible delay in Windows 11.
I measured once. It uses about 50% more resources and offers less feautures (or at least hides existing feautures). You may not have noticed if you had resources to spare.
It does offer some new features for businesses. Nothing useful for the consumer, and nothing to justify the massive performance loss
The Windows computer I have to use at work takes over ten seconds to open the calculator. It literally is faster to type the calculation I want into a search engine and get the results back over the network.
The new calculator even manages to screw up basic input. The old calculator accepted both commas and periods as decimal separator inputs. It just worked no matter what I typed in. The new calculator has some sort of "clever" localization where my inputs change depending on the language of the operating system. My language uses commas so of course it only accepts those. Infuriating. Hope whoever coded this is enjoying their promotion.
Off-topic, but do you know Mozilla Firefox has a builtin calculator and unit conversion in the URL bar? For my personal use I rather use python and GNU units, but I guess for most users that live in the browser instead of the terminal, this could become their default calculator.
browser.urlbar.suggest.calculator = true
I don't know if you need to restore the urlbar first, before that works.
One of the first projects I made while learning to code was a calculator.
It wasn't very sophisticated. But it was fast and it handled commas and periods. It wasn't localized, but it could be.
Sad to think that me having a month of coding experience made a better product than MSFT, yet whoever coded the calculator is probably making ten times what I am right now.
Yeah, I think that is a common first task when learning to program. Learning about strings: write a first-grade-math expression calculator. Learning Java: make a GUI calculator. Now convert between prefix, infix and postfix notation. This is all even before you learn about classes or files.
The new calculator isn't just slow to open, it seems to have actual input lag too. God I miss the old calculator.
To me it's not sad, it's infuriating. This corporation is worth a trillion dollars. Why can't they do their jobs? I'm sure the old calculator could be maintained and improved without screwing it up beyond belief. Send us some fat stacks and we'll do it.
Its AI and not humans that make up that trillion dollars and its AI enshloppification that created the new calculator. You are not AI - no fat stack for you.
With numbers >1000 they are of course displayed with thousands separators as 1,000 (text) now like you would see in financial reports, how attractive. Big numbers have a few commas too. No longer displayed as unseparated numerical constants, like you know, computers have always used.
And if you copy the figure from the calculator display, by right-clicking for the context menu or CTRL-C, you get the whole separated text with commas included to paste into where you need it.
So the receiving textbox you pasted to now needs to have the commas manually edited out before you can go forward, unlike any other Windows calculator.
I guess somebody forgot that people might want it to be at least as useful as it was since the 1990's.
You can still paste plain numeric text in without any commas, it just doesn't copy back out in the same usable format like it always did before.
You can't make this up.
A calculator is supposed to be the perfect example of a no-brainer :\
Edit: If you do the math it must have been more than one person who forgot, you have to think, is it even possible for one person alone to be responsible for quality declines like we have seen on their own? If so who would that be?
Wow that's annoying. Just reproduced the issue on my work computer. It's real. It even localizes the commas into periods too which is amazing because it has the potential to be parsed as a floating point number!
Just for the record, I just timed how long it took for the calculator to open. Eleven seconds. That's how long it took for it to display a window on the screen. A useless blue filled window that did nothing. It took a total of 17 seconds for it to show the calculator controls and be usable. This isn't a loaded machine, it's a freshly booted Windows system that's been at rest literally doing nothing for over five minutes. Notepad opened and was usable in less than one second.
The old notepad would still open instantly so that can't be it. The updated machines with the new notepad are just as infuriating.
Reminds me of the shitty gamer laptop manufacturer apps that would take over a minute to display a glorified rectangle on the screen. All this to configure keyboard LEDs. I reverse engineered that garbage and made a Linux version that works instantly, proving their incompetence.
All I know is it's an infuriating experience that I basically have to speedrun through almost every single day before I can actually get work done. My Linux laptop must be over a decade old by now and it just doesn't have this problem. The Windows 98 computer I had as a child didn't have this problem.
Whatever it is that Microsoft is doing they should probably stop. A goddamn calculator application shouldn't require a high performance workstation to even launch. It worked fine before, now it takes ages and can't even handle input properly. That's stupid and there's really no excuse for it.
With Windows 11, all the stuff going on in the background and so much new excess disk I/O just dwarfs that of Windows 10 on the same hardware.
And that was orders of magnitude more than W98.
Your SSDs are getting hammered like never before.
The first time you open the new, sluggish replacements for old standbys they take way more time to load, but then if you don't turn off the PC completely they are already in memory lots of times so they pop up faster in subsequent times, and with simple things like Calculator the actual calculation is not any slower than it was in 1998.
At least as long as your PC hardware is 20X as fast :\
Its not faster bereft of context, its just bloated. If you have enough resource to throw at it, its roughly the same. Theres some specific things that can themselves be slower, the Windows 11 Start Menu has had a lot of words written about its new implementation.
That _is_ slower. The fact that it's possible to throw enough resources at it that both "look" the same speed, doesn't change the fact that one of them is 10x slower.
I dont know what to tell you. I have endless user complaints at i5 16GB RAM, and none at i5 32GB RAM. Not to mention that I run 32 myself and its mostly fine. I can open menus.
There are a ton of posts and bug reports about the Windows 11 File Explorer being slow. Personally, after a few minutes of use, changing directories can take on the order of 20-30 seconds!
The slowdown appears to be due to XAML Islands, which allow legacy code to use modern MS UI stuff.
This was one of the most outrageous data grab in the past years. They replaced the completely working simple Mail app, which I used until that point, with this garbage, and I was just lucky that I paid attention, and I stopped for a sec what is that warning which tells you that they grab literally all of your emails.
It's been so weird to watch over the decades as team sizes, budgets, and timelines have exploded even as we've abandoned once-normal things like native GUI applications as too hard in favor of "more efficient" webshit... even as the aforementioned stuff with growing team sizes, budgets, and timelines have happened.
>What's weird is that AI is supposed to make development easy enough that native applications are just as fast to build than web apps
The inverse has been happening. AI seems to be best at JS and React, so many projects use this just to have the best results. I think this is the whole reason that Claude Code is actually React that's then mapped onto a terminal.
> make development easy enough that native applications are just as fast to build than web apps
I don't think that was ever not the case. The popular UI toolkits include a WYSIWYG editor where you can pick widgets and just put them where you want them with the mouse. Sure, that might not be what developers like to use, but invoking a widget constructor is not that hard and gets you a lot more functionality out of the box, that you would need to implement in JS.
Cross-platform GUIs is also more of a problem of theory. It used to be a big thing, because the GUIs don't look native to the platform, but that concern has gone out of the window with websites now. Win32 programs run with WINE, which I guess is not desirable for deploying to ordinary users, but I guess the people who write for Win32 generally do not care much about porting their programs outside of MS Windows. GTK+ and Qt both run on MS Windows. TCL/Tk comes built-in with Python and looks native on MS Windows.
Encoding algorithms is not that much different across C-like (Algol-derived) languages. Registering callbacks also looks kind of the same. I guess what makes a real difference is the ubiquity of async in JS, where you would use threads more in native applications.
I think what is an actual difference is the mindset around styling and layout. This is something that you actually need to adapt. CSS is more declarative, much like writing constraints for sizes, because you just write a formula about e.g. size in relation to other sizes. On native toolkits you would need to implement this stuff imperatively, I guess this looks like a real downgrade coming from the web, but it is really just a different mindset. Also when you run on the actual machine you have actual access to the device/viewport characteristics and can adapt based on that, and don't need to write an abstract layout. The other side of the coin is that the default widget packaging mechanism has been grid based while CSS only gained that later.
What I guess is also easier in JS, is just drawing on a canvas. The native UI toolkits want to nudge you into implementing a custom widget which implements all the required functionality of widgets. That results in a way better interface for the user, but when you just want a raster graphic you can click on, it can feel like a huge waste of time.
Since now native toolkits also support CSS, have JS bindings and Webpage targets, a guess the difference blurs.
The user is not the customer. Microsoft builds software for the enterprise now, so Windows 11 is full of new features for the enterprise and has nothing for the User.
They forgot that Enterprises are made out of Users.
> What's weird is that AI is supposed to make development easy enough that native applications are just as fast to build than web apps
Think one step ahead. They will want you to pay them for some LLM "agent" to use the GUI instead. It's not important that GUI is human usable anymore, actually the opposite.
It’s also weird that the productivity increases of AI lead to layoffs instead of hiring. If we can do more with AI why are companies scrambling to maintain the current output? Does leadership lack the vision of what to do with the additional productivity?
Windows 10 explorer.exe is 100x faster than Windows 11 explorer, it's not even close.
It also signals the death knell for Windows native apps. Microsoft can't make them anymore. It won't be long until even Excel is a Electron sloplication.