Web apps tend to be a mixed bag. After a while they become slow because of dozens of async operations relying on network.
replyThat can be an issue for native apps too, but they tend to be designed in a local-first manner, which means that they'll always have a speed advantage, assuming your typical dev team.
Another way to say tenth of a second is 100,000,000 nanoseconds.
replyWe have 4GHz computers with 8-16 cores, and it takes 100,000,000 cycles to show the start menu?
Edit: Corrected the scale factor.
Another way (which happens to be correct) to say tenth of a second is 100 000 000 (one hundred million) nanoseconds. You were off by a factor of 1000!
replyYeah, I skipped microseconds entirely.
replyAlso, at a typical turbo speed of 5 GHz you get half a billion clock cycles and multiple instructions can be retired per clock for about one or two billion total in those 100ms.
replyThat’s about 1,000 instructions per pixel of the Start Menu!
All web apps are in fact slow compared to native apps. They are also clunky (though that's my opinion, not a fact). There are better and worse web apps, yes. And it's possible to make native apps which are even worse than a web app. But "like all web apps, it's slow" is a perfectly fair statement.
replyWhat native apps is Microsoft developing as of lately?
reply