Then should we also exclude ...

You (and all the others that sit behind your royal we), should not exclude anything that you individually or collectively find useful. I described my distaste for frameworks, and my reasons. It is up to anyone else to reach their own conclusions.

I can't. I've never used any of those. I've created my own :) But it does not mean that it is not possible.

Oh, it is possible to use event-driven logic within a threaded application. For example, Tk's event loop runs just fine within a thread(*). The same is true of Prima & Wx. And OpenGL. And Win32::GUI. And any event loop constructed around select, even when encapsulated and simplified through the use of IO::Select work fine in threads also.

(*)Though you do have to be careful not to try using tk objects across multiple threads.

So there is no fundamental incompatibility between threading and event-driven programming.

But--and this is the whole point--all of the above are libraries! Not frameworks. And it demonstrates exactly why I like the former and dislike the latter.

With libraries, I call whichever library best serves my needs, whenever I want, and in whatever combination I want.

With frameworks, I have to try and remotely manipulate them into calling me at the appropriate time to do whatever needs to be done, and they fall in a heap around my ears if I do something they don't like.

(Well written) Libraries good. Frameworks suck! (But each to their own:)