

Developing cross platform native apps sucks a lot no matter the tech stack. Compared to web technologies where the burden to follow the spec is the platform if they wanted to have interop with the web, the dev doesn’t have to fight the platform.


Developing cross platform native apps sucks a lot no matter the tech stack. Compared to web technologies where the burden to follow the spec is the platform if they wanted to have interop with the web, the dev doesn’t have to fight the platform.


Linus called that a good sign, while asserting that he is “much less interested in AI for writing code” and more interested in AI as a tool for maintenance, patch checking, and code review.
Linus knows where the actual problem is in the software development cycle. Not that human code slower but the approval of the code itself is slow.


That’s the thing. It doesn’t break it to the point of unusable unlike other patches I think. So the test didn’t catch this since performance is rarely a part of a test suite no?
Then why can’t QT provide the same benefit of delivering cross platform developing experience? See, that is the core issue. You write FOR the platform not for yourself. In the web space, the platform writes FOR you lest they want to break compliance with the rest of the web standard. When you are writing web application, you are writing program in a standard that the platform WILL follow instead of you following whatever the platform dictates at the time of their convenience