Hacker News Reader

Microsoft go to great lengths to do everything possible to make that backwards compatibility happen.

only after the last 32-bit version of Windows 10 goes out of support will some of these things begin to get fixed. and even then it will not be a priority.

View on HN

This isn't just for backwards compatibility, OutputDebugString is a crucial function and hasn't been replaced with anything afaik. We use it all the time. Why fix something that isn't broken I guess?

Indeed, that is the very definition of backward compatibility.

This is closer to forward compatibility: your program written for Windows 10 will work as expected on Windows 1.0! Well, at least the OutputDebugString parts.

No. It’s not. If it was superseded, and still kept in, that’s backward compatible.

Reply on news.ycombinator.com