Probably skill issue on my end tbh but here goes:

I'll admit I've never tried GTK. I've always assumed it was specific to linux and used to make apps that look a certain way (like they were made for gnome) vs allowing you to make UIs the way you want to. Maybe I should look into this more.

Qt I'd say is "industry standard" but I've never been able to figure it out (so definitely skill issue here). It's just that every time I've tried it, it's been confusing where you're even supposed to start. Also the last time I tried it I was a bit lost because I assume that I'm supposed to use Qt 6 (?) but it requires me to create an account because there's a whole community/enterprise pricing thing (fair enough, nobody's entitled to OSS work, especially not billion/trillion dollar companies). I plan to look again but that's where I've been stuck so far.

I hate shipping chromium for every single app and it's easy to fuck up a react app but there's something to be said about cutting through the BS, just building, and having it work the same everywhere. Webapps won't perform as well as native but they will perform well enough that it's fine assuming the product owners give a shit.

Still learning but this has been my sentiment so far.

Edit:
Been playing around with iced.rs a bit and it looks promising but I haven't done anything past beginner stuff so no fully formed opinions yet.

Also there was a big push for "web first" applications, thus there's a lot of developers with that kind of knowledge. In college, I was instructed to instead of learning software optimizations, to learn how to outsource complicated computations to the cloud, where there will be always enough compute, so I can write my code "as clean as possible, without worrying about optimizations".