@samebchase i’ve been thinking about this problem a lot (and not just this week). the line any toolkit or library or framework needs to tow is between the ui on one hand and the platform on the other.
going all-in on something like flutter is basically saying “all your platform are belong to flutter” where one eschews control for platform agnosticism and widgets that aren’t widgets at all. in a world where programmers pride themselves on min/zero deps, flutter is the fuck-it option: depend on a massive pile of libraries and abstractions and hope google never rips it away from you.
this makes *some* sense on mobile where ios and android and {future-mobile-os} aren’t interestingly different.
but the desktop is a cluster. it’s still reflective of the 80s and 90s when its design emerged. if macosx hadn’t happened, there would be 3 very different targets to hit. now there’s effectively two. but windows is a doozy.
it gets worse as win/mac rot — how long until users can only install “apps” from a store?