Why didint tom schkimansky go with PyQt5?

[Schkimansky]

I saw your response on this question:
#1461

I never knew customtkinter was slow until i checked its code and saw theres a entire rendering engine based on the tkinter canvas, Further more i found out that drawing rounded squares is not possible in the tkinter canvas so you have to make that too.

Ive made a few UI libraries, And ive based it on top of PyQt5 for my current one, Since i found that to be reliable, flexable and BLAZINGLY fast (Like really, its made in c++).

And already i have a few widgets ready for use with a nice CSS Flexbox re-implementation.

Considering how fast and amazing Qt is, Why didint you make CTK or the CTKDrawingEngine on top of Qt? I mean you could keep the arguments same as tkinter but use qt under the hood. And i have found this to be really nice as of development experience, And speed.

Tkinter is nothing compared to Qt, So i cant seem to know anything that Tkinter has yet Qt doesnt.

Was this an unconscious decision or you didint know about qt/pyqt at the time? Or maybe you found Qt hard to use? (yes, its really hard to use)

Also transparency is a NIGHTMARE in tkinter, You definetly had to deal with that alot lol. Theres no RGBA, Only rgb

I am curious about the reason and would love to know your intentions.