3 ms·
Qt not using std::string made a lot of sense when everyone though UTF-16 was the future. A 16 bit default string type was just what modern i18n friendly langua
by sgerenser 6y ago
Qt not using std::string made a lot of sense when everyone though UTF-16 was the future. A 16 bit default string type was just what modern i18n friendly language or framework had to have. It’s only in the past several years with the rise of UTF-8 everywhere that it looks like a mistake.
- PaulDavisThe1st 6y agoI'm not questioning your perspective. But I looked at using Qt in 1999 and easily decided against it, in part for this reason. Those of us coming from a *nix background got the UTF-8 thing much earlier than people affected by the Microsoft worldview.
- pjmlp 6y agoAh that is why C excels in localisation and internationalisation. Thankfully having a *nix background helped Sun getting Java design regarding UTF just right.