Plenty of folks use WMs like Sway that don't use GTK or QT and everything is fine. You just pick a theme and it gets passed to GTK and QT apps. I guess if you show decorations, they differ between apps, but it's really not terrible. I think we're all used to that by now, on every OS.

I'm not talking problems with DE toolkit applications. I'm saying that without the additional incentive to round down the sharp edges in Gtk3 with a custom distro patch set to get their DE working right (they won't have to because it's not gtk) they probably won't maintain the aformentioned required distro patches to gtk to fix all the frozen in bugs/feature removals. And so running gtk applications (most linux GUI applications) on these distros is more likely to have these sharp edges.

Pop!_OS is still based on Ubuntu, so I doubt that they are going to ship unpatched upstream GTK, it's more likely going to be patched by Canonical.

Unfortunately Canonical does not fix gtk3 either. Ubuntu after 14.04 is broken and you cannot paste file paths into Gtk3 program's File-Open dialogs without an elaborate key sequence to bring up the pathbar first. But it is fixed in gtk4, which Gnome uses, so Canonical doesn't care.

We will have our own file dialogs as we complete the Iced GUI library.

I remember running GTK apps on KDE desktops just fine. Why wouldn't I be able to run GTK apps on their ICE powered desktop?

Re: web - isn't the purpose of WASM to make possible in web environments that which is possible on desktop environments?

> Why wouldn't I be able to run GTK apps on their ICE powered desktop?

Of course you would be able to, just don't expect the theming to match, the menus to have similar structures, dialogs having buttons in predictable places, etc.

> isn't the purpose of WASM to make possible in web environments that which is possible on desktop environments?

I don't think so. I think this is the purpose of all the new Web APIs more than WASM. The sandboxing and the inability to call out to the system is crippling for GUIs in WebAssembly. It works well if you control the drawing and are able to output raw data to a <canvas>, but it's a hassle. WASM works the best for things like opencv or dlib, but I think the GUI for the apps compiled to WASM will need to be written in JS for quite some time, if not forever.

> Of course you would be able to, just don't expect the theming to match, the menus to have similar structures, dialogs having buttons in predictable places, etc.

I think nearly all Linux users - and most Mac/Windows users who don't remember how things were back in the XP or classic Mac era - don't realize these are even goals or something that has ever existed.

I remember exactly how things were with Windows going back to Windows 3.0. This never existed on Windows.

It does feel like an odd complaint. I have had mismatched desktop elements for a very long time now. What's another oddball entry on the list?

Rest assured that anyone with experience with a GTK3/4 application is going to have an easy time with the COSMIC designs. A lot of aspects will be similar. Maybe even a bit more standardized in some ways.

Maybe they mean aesthetically? KDE basically makes a clone of their Breeze theme for GTK to try to make all apps have a consistent look on KDE. I believe the reverse is true with an Adwaita theme for KDE/Qt apps, but don't quote me on that.

The same is true with an Adwaita theme for KDE/Qt Apps. I used to do this on both, Plasma and GNOME.

These days I style my Qt/KDE apps all Breeze on GNOME and vice versa when I am on KDE, because unfortunately icon sets just don’t match up and I've run into 'invisible buttons' issues way to often.

As long as both are in dark/light mode I find this way less annoying than having to hope for a good enough tooltip on mouse over (or just tap and see on mobile).

You can find versions for both "toolkits" even in custom themes. For the end user it's mostly a non issue. Even with different backends it looks more consistent than Windows.

That's true, but the Iced theme that they're showing in the images looks like it would be very difficult to recreate in GTK and Qt. That's not mentioning the increased amount of time and effort in maintaining those themes. Perhaps this is an area that the community will contribute to though.

Color palette adjustments alone would bring it pretty close. We can automatically generate them on the fly.