Hacker News Reader

Comment by djrogers | Hacker News Reader

> An iPad would struggle to do one of these at a time let alone all of them at once.

You haven’t touched a modern iPad, have you? Not only do they not ‘struggle’ to do one of those at a time, they’re butter smooth at it. The workflow/task juggling aspect is definitely an issue, but there is nothing preventing an A10x or A12x iPad from doing any of those things with all the performance you’d expect from a $3k+ MacBook Pro.

View on HN

GP is talking about how the design of iOS is preventing one from doing all those tasks in a satisfactory way, but not the hardware.

For example I could be editing a movie and waiting for it to export. Then I switch to a different app and start editing my photos. There is a Task Completion background API to allow the former to continue to run, but there is no guarantee nor any notification when iOS decides my new photo editing app is consuming too much resources and jettison or kill the movie app. It contributes to this nagging feeling of needing to switch back to the background app so that iOS would keep it alive.

It's just an app management model ill suited to professional work.

As a workaround, you can put the app into split screen and the OS will keep it alive because it is still in the foreground.

Seems like trying to do anything serious on an iPad is a story of one workaround after another. Why would it be worth the hassle?

It's thin, light, and has better specs than my laptop?

I own an iPad Pro for reference. I should have been more Clear: while the iPad can do some of those things and certainly the hardware is good enough, iOS dowsnt fit my use case well (doing lots of things at once).

Pro-tip: Don't do lots of things at once.

Reply on news.ycombinator.com