15 ms·
I think the reason QString was necessary was because STL's std::string was just really lackluster (and still is). The problems: - An barebones API that's hard
by cyber_kinetist 4y ago
I think the reason QString was necessary was because STL's std::string was just really lackluster (and still is). The problems:
- An barebones API that's hard to use (missing really basic functions like contains() and split(), although they might come on C++2-god-knows-fuck-when)
- Until recently (C++20), didn't have a convenient way to format strings. QString::args() isn't that nice, but at least it's far better than using the stream operators. It's just sad that people were hyped that std::format was finally coming in the year two-thousand-fucking-twenty...
- Dealing with encodings and locales. Unicode conversions, anyone? Like, C++17 actually even deprecated the whole <codecvt> header! I understand it was absolute shit, but the audacity to remove it without presenting an alternative...