I hope one day Microsoft will remove support for arbitrary 16-bit code-units from their API and only accept valid UTF-16. That shouldn't break too many applicat

I hope one day Microsoft will remove support for arbitrary 16-bit code-units from their API and only accept valid UTF-16. That shouldn't break too many applications, but will finally allow people to use unicode strings to handle filenames. Switching the default "ANSI" encoding to UTF-8 (or WTF-8) would be pretty nice as well, unless an application is running in compatibility mode. That should avoid most of the problems with the 8-bit API, without breaking everything. And in the long run perhaps even switch to UTF-8 internally, making the 16-bit API legacy (one can dream).