Windows NT on 600MHz machine opens apps instantly. What happened?

Why is Win11 so slow and unoptimized that it needs such crazy hardware.

I don't think it's unoptimized as much as it's extremely bloated.

What's the difference?

/s

Bloat is intentional and fills Microsoft’s wallet.

Optimization drains Microsoft’s wallet.

"Bloat" includes the addition of intentional, but frivolous, features. An application can be well-optimized but still slow simply because it's doing too much.

But I think the reason that most modern software performs badly is because of optimization: we're optimizing to reduce production costs over increasing performance.

It's economic in nature. We minimize production costs by using frameworks and other labor-saving tools. The code produced using these tools tends to be poor, but hardware is cheap enough to make up for poorly performing software.

It's an intentional decision.

Some of that bloat is useful. Windows indexes files in the background, which would choke a single-core machine with HDD for sure. Thanks to that I can quickly access my files... well, so long as Windows is able to find the correct thing...

> Some of that bloat is useful

Well, all of that type of bloat is presumably useful to someone or it wouldn't have been written. That doesn't change the fact that there's a cost for including it.

> Windows indexes files in the background

But here's an example of the tradeoffs. I hate this behavior. It incurs an overhead that provides no benefit that matters to me. So, your useful feature is my useless bloat.

Everything's a tradeoff.

Expect that the search totally sucks. Have you tried Voidtools Everything? It finds files instantly, even on filesystems with millions of files. Yes, instantly, you type a word and it's just there, no matter SSD or HDD. Windows' built in search is a complete waste of time.

> But here's an example of the tradeoffs. I hate this behavior. It incurs an overhead that provides no benefit that matters to me. So, your useful feature is my useless bloat.

Turn it off then?

Yes? That doesn't affect my point about it being a kind of bloat.

The term bloat (as it applies to software) is rooted in gamer-think that has no basis in reality and sends a strong signal of lack of understanding. It's reminiscent of the days of 'BlackViper' and disabling Windows Services -- again, another gamer lack of knowledge issue.

The new Windows Terminal is also extremely slow for some wild reason

> Some of that bloat is useful.

If bloat is useful, notepad in any form on any version of Windows is bloat by definition.

You've got CLI editors that are smaller.

A meaningless term to deride a feature or service you don't like or use.

And yet when I want to search in the files in a folder searching with windows search won't turn up anything, so I have to switch to the WSL and grep...

Empty notepad, just started. 82,416K working set in main memory. 25.7MB in dedicated GPU memory. 59 threads. 2 billion cycles spent since launch.

Two threads in !OpenAdatper12 spending ~1.5M cycles per second. Two threads in !recalloc spending ~256K cycles per second.

As shipped, this is no longer a single executable, it is a collection of 230 files, totaling 10.5MB, about half of which are bytewise duplicates, and another significant chunk have overlapping responsibilities, between the icon fonts and png icons.

"Software bloat is a process whereby successive versions of a computer program become perceptibly slower, use more memory, disk space or processing power, or have higher hardware requirements than the previous version, while making only dubious user-perceptible improvements or suffering from feature creep." -- https://en.wikipedia.org/wiki/Software_bloat

I'm not aware of any substantial new features. It uses a new renderer, but this does not produce a significant observable difference from the previous one beyond using more memory. It supports dark mode.

A graphical user interface? Just bloat.

Ships with a TCP/IP stack by default? Just bloat.

Mouse support out of the box? Who would want that?

Indexing is a weird example to use considering how notoriously garbage Windows file search is.

For some reason even in fairly constrained subtrees it takes forever to find file names.

> Windows indexes files in the background, which would choke a single-core machine with HDD for sure.

This was done also in Win 7. It didn't have such a performance hit, but it was the first thing to be disabled after installing windows.

Windows has been indexing files for over 20 years.

Back then I would turn it off as I didn't find the search function that usable, and more than once I've had a "clean and build" process fail because some file was open and being indexed, and since Windows locks files on read, the build could not delete the file and just aborted. So, I turned it off.

Also full unicode support on high resolution screen.

I'm no gamer, and "bloat" has been a term used in the industry from well before "gamers" (in the sense used today) existed. It's been a term of art for over 30 years.

It also describes a very real thing.

While there are a lot of things that everyone would agree counts as "bloat", there are also areas of disagreement in the form of "one person's bloat is another's essential feature".

C64 lovers would likely agree with all of those points.

New renderer, dark mode, auto save, resume on open, HiDPI, tabs, and I'm sure a lot of things I'm forgetting.

Don't forget what Notepad.exe truly is -- a testbed for new technologies. It's not "just a text editor" to Microsoft.

Launches into PoSh 7 x64 in <1s for me on Win 11.

It only searches the names.

It’s also searching the contents. Try turning that setting off.

And then 'everything' search tool came with instant fuzzy find. A strange experience after years of buggy and slow MS indexation.

Even when you turn the search indexer off, the indexer background service still seems to be doing ... stuff.

I have a Windows 10 VM I use for some testing and such, and all these background things keep using up huge mount of resources, no matter what knobs I turn and regedit levers I pull I just can't get it to stop.

For comparison, I also have a macOS VM which certainly isn't fast, but nothing like the Windows one. And the BSD and illumos VMs work basically fine (although in fairness they also don't start X11; but I do just ssh in to all of these machines and never use the GUI for anything).

I feel like this is something where determinism would be a win. Maybe have indexing, but pre-prioritize certain common searches.

I notice that I get completely different results on my home and work machines doing the "start button, type" search. for "Downloads", expecting C:\Users\Username\Downloads, the home machine figures it out after three characters. The work machine seems to have decided that I clearly want "File Explorer, not any particular directory" and "Change how I download updates in spite of it being a corporate-managed box where I probably can't push that button without asking IT to remote in and do so" are what I want, even when I spot it the whole directory name.

On Linux machine I can access and find my files fast. And without any indexing running on the background. Shit... even I could run the OS from a rust HDD and be usable without pain. Windows10/11 without an SSD it's painful slow.

Index for what? The Windows search has always been unbelievably bad and it has only gotten worse since Windows 7.

Oh but that's just Amiga envy.

But if you turn it off, you don't get the start menu indexed anymore. I don't need my files indexed, I just want my start menu shortcuts indexed. There's a few other small things that no longer work without indexing, though I forget what they are now. Everything is great, but there's actually other services that depend on search being enabled, as it tells you when you try to stop the service that is shutting down dependent service first.