4 ms·
> A big point of Qt is that you have a complete consistent library with an event loop that will handle everything from GUI to network / serial port communicatio
by tialaramex 4y ago
> A big point of Qt is that you have a complete consistent library with an event loop that will handle everything from GUI to network / serial port communication / media playback / JS scripting / database access / ... transparently
A kitchen sink library, re-implementing absolutely everything. I do mean everything there's even a QString to use because heaven forfend a C++ library wouldn't have its own custom String class...
The temptation to build kitchen sink libraries is exactly what this proposal seems to be fighting. No, I don't expect they will win.
- pjmlp 4y agoKitchen sink libraries usually work in all supported platforms, no need to play tetris with OS and compiler version support.
- cyber_kinetist 4y agoI 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...
- jcelerier 4y ago> A kitchen sink library, re-implementing absolutely everything yes, and having written projects in both the kitchen sink and the many-libraries approaches, the one that consistently shipped software fast is the one with the kitchen sink framework