Or maybe your expectations from ai detection are too high.

I think this one is better https://youtu.be/4rTv9wvvat8

I mean if they would produce a better UI by using their expertise, how would not becoming an expert in the new thing be better?

I failed to understand the meaning of this sentence. It doesn’t make sense to me. Producing a better ui is not even on the table when we are talking ui frameworks and native programming - you use what’s available, and if you are a graphics designer then maybe you should’ve sticked to that instead. Becoming expert in native ui is super cool but I wouldn’t expect such miracles from everyone. Just producing a valid low level code is enough to meet my standards of performance. That’s because those standards were heavily affected by web frameworks existence.

The reality is that the people paying the engineer are going to want the better UX

And I hoped it would be customers who would pay for a software or a service who would send valid feedback.

AI can assist you if you more-or-less know what you’re doing

Assuming web devs creating apps don’t know what they’re doing?

but a novice replacing proper learning with ChatGPT pairing is going to write some shitty code.

Chances are that code would be much more optimized than anything electron/CEF wrapped.

to actually be up to our code quality standards

Quality standards are great. But seeing companies shipping fixes to simple CSS issues that were breaking some of main app functions made me realize most of them don’t care about quality standards. If that’s how it is and if there will still be a lot of broken stuff across app updates - might as well just go all the way to proper low level languages.

but no one is going to become an expert in something overnight

It’s not like they need to become experts. But also that’s actually possible (at least the effects of that), especially with all the AI around.

Because optimized software is better for industry, people, and environment. Also seeing that some menu or window is not an html page but a native element makes my headache go away because I value my CPU cycles (seeing a cursor doesn’t lag when some complex page is displayed should not be considered a weird fetish) and like it when things don’t do stupid unnecessary stuff both visually and under the hood.

And it could be even less than that depending on specifics.

That’s a very bad way to look at things. Just because I have gigabytes of memory doesn’t mean I want to use unoptimized software.

I’d rather not have frameworks based on web browsers. Programming is not that difficult.

“Only”

You don’t understand. This way if some app crashes it will not cause others to crash too.

This is how google introduced the “multiprocess architecture” of Chrome.

Love the absence of logic in these messages. Next time it’ll be “pay $2 to continue” or “do a barrel roll to continue”.

Why is it 37 mb? Stock Samsung sms app is 2 times smaller.

How about shoving them into the Options screen instead?