Hacker News new | ask | show | jobs
by simulator5g 98 days ago
Microsoft is responsible for the UX of the ecosystem they create. Things that extend the OS are part of that responsibility. It shouldn't be possible for such a thing to happen. The OS could just show the damn menu after 500ms even if some extension hasn't responded.
2 comments
Rohansi 98 days ago
The extensions are native code loaded directly into the Explorer process and called from the UI thread. There is no async option they can time out.

It's not the recommended way to hook into the context menu. They have had declarative options for a long time which do not cause issues like this.

link
p_ing 98 days ago
The reason the Windows 11 menu changed was to solve for this exact issue.
link
simulator5g 96 days ago
I don't have anything that hooks into the Windows 11-style menu though. The only additional options in the "Show more options" / Windows 10-style menu are Nvidia stuff which comes with the PC, and Visual Studio, which is Microsoft. This is not caused by some crappy 3rd party app.

The new menu is faster, it takes about .5 to 1 second to appear. Pretty great compared to 10 seconds for the old style menu. Still a very noticeable lag for a simple task on a top-shelf Windows laptop.

To be fair the delays get better when you repeatedly open the context menu. It seems to get everything cached and then it loads in ~0.5 second. But it loses this speed when you don't open the menu for a while.

link