Take

Almost eight and a half years ago, I switched to using an iPad as my full-time computer, having come from decades of having Macs.

[..]

I’m reminded of YouTubers who say that they tried using something as their main whatever for a whole week; well, I did it for eight years. Allow me to report back.

[..]

The thing is, there’s a lot of momentary waiting with an iPad. Waiting for it to disambiguate a tap from a swipe or a scroll, or from a tap-hold or a drag; waiting for it to do its required ritual animations in the summoning or banishing of an app or a section of UI; waiting for it to thaw or resurrect a process that fell foul of its ferociously aggressive limits on things running in the background. Everything goes at a glitzy demo’s pace, rather than at an I-already-know-what-I’m-doing pace. If you think of your tasks like the words in a sentence, the spaces between them are longer on an iPad, like fully-justified text that’s expanding to fill the line. It’s definitely bearable, but it adds up.

[..]

Presumably because of the legacy and the architecture of iPadOS, many activities simply fail if not kept frontmost. Take Final Cut Pro, for example; a first-party app which you’d assume would have every available privilege and priority, especially given its resource-intensive workflows. After triggering the export of a video project, doing anything which moved Final Cut from frontmost status causes the export to fail, instantly.