Maybe I&#x27;m conflating several of my issues with webapps in the word &quot;toy&quot;. One thing is ergonomics, bloat and lag issues. But the other thing is that webapps trying to fill in the role that originally belonged to desktop apps are more often than not pretty dumbed down. There are several reasons for that - one is performance, which makes you unable to add more complex features without making the entire webapp unbearably slow. Another is the business approach of sticking to MVPs and not really progressing beyond them.<p>Also, lag issues are not really limited to high-end graphics &#x2F; video editing. Sure, lag&#x2F;low performance makes those tasks basically not doable in the browser. But even &quot;ordinary&quot; webapps - like word processors or issue trackers - are annoyingly slow. Take Jira for example - I&#x27;m probably wasting a few (billable) hours every month just because it&#x27;s not a desktop app. So are all of my co-workers. It&#x27;s most likely also the reason people tend to batch time reporting and do it once a week or so (it&#x27;s much less distracting then), which as a result precludes management from having access to up-to-date information about time spent on tasks.<p>Trivial inconveniences can have non-obvious impact.