At least a quarter of my tech issues is finding out how to turn off some idiotic misfeature. Meanwhile, features people have actually wanted for 40 years are still missing.

I just turned off the Windows snap feature. Not for the first time mind, it keeps coming back. What I would like is a way to save all my personalization settings I have changed and reimpose them.

A constant annoyance using Inventor or any similar program where you have a thing you have to convert to pass it to a different program is being asked 'are you sure you want to overwrite' every damn time.

Its not just that I want the prompt gone, I want the file system to distinguish between source files (C, C#, Inventor, Word, etc) and generated files. The backup system should be smart enough to know it doesn't need to save generated files unless they are specifically marked as precious. And that should be something I can specify globally, if generating an output takes hours of CPU, it is precious, if it takes less than a second it is not.

I don't just want to get rid of the annoying 'are you sure' prompt, I want to eliminate the need for it entirely. When I open a project in Inventor or Premiere, I specify the output formats I want (e.g. .step, .stl, .mp4) and these should generated for me automatically and intelligently depending on how long processing takes.

When I attempt to access a file in another application, this should cause the file to be generated automatically if the file is stale.

This is make functionality built into the O/S and file system. Yes, it would require some additional affordances because some conversions have options and you need to select different options for different outputs but that is another area for workflow optimization.

I take photographs on the Nikons in .raw format but most applications require .jpg or .png. A while back I wrote a program that pulled the images off an SD card, verified the copies and erased the card. It saved the originals to one directory and small and large jpg images to another so I could easily view them on the iPad, send them in mail, etc. So 2026_07_1_001.raw became 2026_07_1_001.large.jpg and 2026_07_1_001.small.jpg.

All that functionality could be built into the O/S and accessed on demand with the machine making intelligent decisions about what outputs to generate ahead of demand, what outputs to purge and what outputs to keep. It is a caching problem and we know how to solve those.