Detectors can clearly identify the exact issues. So, what are those issues here? We know, but we don't want to tell our cash-paying customers.

It was written in the AGENTS.md, but Claude only read CLAUDE.md. That is how the man-vs-machine war started.

I work on the IUP fork, where I have and support the Qt driver, which works with both Qt5 and Qt6, and I only need a couple of checks to make it work on both. I often check if I broke the Qt5 build; nope, all good there, hard to break. For GTK3 and GTK4, those must be separate drivers; there's no way you can handle that with a couple of checks. Everything is different. That was possible to some extent and works with GTK2/GTK3 (single driver), but there are so many checks and workarounds there. Qt is so nice to work with.

I am working on the IUP fork (UI toolkit) , with many new drivers/backends and features, and, of course, I added Haiku because it looks and performs so well, it works differently from what I used to see, making it even more interesting. The result: the absolute king in memory usage was the Win32 driver, like 4M for Hello World; in Haiku, that is 3M! For comparison, the GTK4 driver uses 40M; GTK3 and Qt6 ~15. WinUI is something like ~25.

My first association when someone mentions Matrox is MPlayer and mga_vid kernel module. I had G200, and hardware YUV acceleration worked perfectly. Direct access to hardware from MPlayer, it worked very nice, in console with `-vo mga` and in X11 with `-vo xmga`, there was no difference at all.

I heard this repeated many times. You can create closed-source Qt apps without paying any money. You cannot statically link, though; you must obey the LGPL license; that is all. And yes, you cannot use commercial modules, but that is kinda expected.

Nice, I just use lxqt-openssh-askpass, but I am on X11. A lighter alternative (for single-text input) would be FLTK. Version 1.4 is really nice, with Wayland support, and they even draw custom window decorations on GNOME. Both Cairo and FLTK should be able to compile with -X; not sure, though, about the status of the Zig bindings.

fltk is c++ based which makes language bindings significantly harder in general. gtk is c based which worked out really well in that aspect.

Sure, you need to wrap it in C, but there is also `cfltk` that is maintained and used in Rust bindings. Btw., the difference in memory usage is huge with GTK4. FLTK hello world is ~10M, GTK3 is ~15M, GTK4 is 40M! With Cairo rendering, it's about 30M, but still a lot.

GTK4 memory usage is ludicrous

ah neat, I wasn't aware that cfltk was already used by rust.

There is cflt and Freebasic FLTK

Why not fix all the issues with private jets and yachts first? Why don't they use regular public transportation as we all do? Instead, let's bash poor Clanker, who reviews kernel code.

Well, AI or not, it is interesting to see Swift and Flutter without Dart. But is SNI Tray there? I see something in the top-right corner of that panel, but I'm not sure what it is.

There is no SNI tray yet. Top right corner is network, battery status.

Yes, and you need an army of people to "wrap" WebKit just like that. E.g., the WebKit port on Haiku, of course, is not in good shape because it has more code than the whole of their OS. EFL once had a WebBrowser control/component, maintained by Tizen devs, but of course, it has now been removed. There is no manpower to maintain such control.