4 ms·
Well, when windows NT was getting implemented UTF-8 hadn't been invented yet. Also as Windows NT was a new OS, there wasn't a big need for backward compatibilit
by gpderetta 6y ago
Well, when windows NT was getting implemented UTF-8 hadn't been invented yet. Also as Windows NT was a new OS, there wasn't a big need for backward compatibility.
- chrismorgan 6y agoThis was most importantly about backwards compatibility with files. You definitely still care about that cross-platform. (Sure, there is also the API split where now you have two sets of functions, the A and the W variants, so that UCS-2 made things much more complicated for ever after, compared with implementing Unicode as a code page, by whatever means. Compatibility was not quite such a big deal there, though the approach they took seems to me to have been a poor choice. Again there were reasons why they did it the way they did, but those reasons have aged very poorly.)