Hey, that was me (JeffMill). I was a dev lead for the Windows shell team at the time, and I got frustrated with notepad not getting any attention, so I spent a weekend and made the changes you describe and more, and had one of my reports code review it. I checked the changes in, and that week, some of the members of test team (remember those?) had a cow and my lead pulled out all of the changes.
I'm still at MSFT, now as an architect, so it turned out not to be a career limiting move, but I certainly should have discussed my plans more broadly rather than just "cowboying" those changes in.
Small world, I worked with you on the Windows Update team. Hope you are doing well. Good to see you here on the HN forum. I also remember the notepad incident!
I love Notepad. I love the .LOG feature. I hit F5 for fun.
For some reason, the dead-simple text editors have always fascinated me. It's damn near good enough.
My app is even part of their compatibility test suite (they asked me for permission and a license).
I understand the need to move forward and that BW compatibility can be hinder that, but it's really frustrating for me to 1) respond to thousands of people asking why it doesn't work after they upgrade, and 2) lose income because there's nothing I can do to make it work the same in Windows 11.
Removing functionality is a bigger problem.
Well, it had a good run. Should such compatibility forever hold Windows back from making breaking changes to those APIs though? 20 years is an eternity in computing...
There is no "need to move forward".
https://blogs.windows.com/windows-insider/2021/12/08/announc...
See: https://blogs.windows.com/windows-insider/2018/12/10/announc... and https://devblogs.microsoft.com/commandline/extended-eol-in-n...
If the answer to any bug report is that the buggy behavior is now the baseline standard, what's the point in reporting any bugs?
Books on Excel programming explicitly call out this issue. This is one thing I definitely would not want fixed.
You will break countless workflows that have operated for decades.
For instance, Unix LF support was added to Notepad back in 2018 (at last!) with a few registry switches for compatibility.[1]
[1] https://devblogs.microsoft.com/commandline/extended-eol-in-n...
I'm not entirely clear whether the "current" API set called "WinRT" is the continuation of "Windows RT". It sounds plausible but it could just be Microsoft being terrible at naming.
Wait what, external software calls into notepad?
Patching other people's binaries, turning off features if the app making the request is "problematic-app", re-introducing bugs, fixing should-be-impossible-to-happen calls from programs that were written by hand, it's all there!
Oh good grief.
(Not saying the approach should be the same, just wish the attitude and motivation were as intense and that Win 10+ were less user-hostile.)
Hobbes: This is so stupid.
External software calls into everything. Welcome to Windows development.
It's extremely difficult to implement even "obvious" changes like a dark-mode Notepad when it could potentially break customers who have been depending on specific behavior for decades.
This is why they've had to write shim-specific code for certain vendors. The desire to move forward versus the awful prospect of having to keep those shims in place.
Or when page resize based on different printers breaks page appearances?
Microsoft, on the other hand, sees that some app calls an undocumented internal function, or has a bug that causes it to misuse an API call that just happens to still work correctly, or even worse, hooks into a system library or something, and considers that now to be a part of the public SDK that is to be maintained and made compatible with everything that might use it, forever.
I don't know if anyone even owned Notepad or any other older inbox apps like the command prompt, but the issues were pretty well understood and WONTFIXed. Single undo, unicode support, unix LF support, etc, etc.
For Notepad a frustrated engineer had produced a change-set to fix all of them, and it had sat there attached to the bug for some time. It would surface on internal mail threads from time to time as a joke or a bitter reflection on bureaucracy, and if I recall a VP once chimed in to say they had looked at it, and sadly none of it could be committed due to backwards compatibility issues.
Of course the compat issues were real (you could view reports on which obscure apps hooked into this or that internal code of cmd.exe or Notepad and would break), but I always though they served as a nice justification for whichever investments were being made at the time: certainly not Notepad.
It's nice to see the wind change on that, even if it took a decade or two.