Originally posted by Luke_Wolf
View Post
I know this very well, since I wasted a lot of time with QT, and building on top of sh*t. I don't see any hope of QT to change. Also the new Vulkan stuff introduced by QT, exactly like the new "QT3D" has the same old-fashion, horrible, and hard to maintain API. [The reason is consistency. Consistency is good and important, but not when aiming for being consistent with sh*t].
And what does rewriting bring? Easy: The earlier, the less painfull it will be. QT is introducing all the time new features.... mostly experimental and full of bugs. And you spend time with QT, you build on top of it, then you inevitably get across the horrible bugs, you make a bug report, it's flagged as "critical". At this point your hopes are big for a bug-fix, till comes the disillusion and many years later you still have to notice that it was not touched in any sense. You are stuck, and then you can choose.... to learn all the Qt internals, understand all the sh*t and try to fix it yourself, then you hope that your fix will be merged, you wait again... and with big chances that nobody cares. Then you can choose to have your separate QT, which gets out of sync with the original.. etc... etc... it's like a chain reaction of sh*t. And in the end you have to notice..... that with all that effort and lost time, you could have written the needed tools yourself and not depending on qt anymore.
Even you get past a horrible qt bug,.... the next ones are around the corner... and you depend on a 90s style c++-API, which makes your own code more complicated, harder to maintain and watching out for leakages of the raw pointers... (especially for the newer additions with less documentation, where it's not clear to whom the raw pointers belong.... to you or to the qt framework which might do the destruction, etc......)
A nice story, somehow related: https://medium.com/message/everythin...n-81e5f33a24e1
cipri
Comment