News for hackers. Stuff that matters.
Re:Building iPad Pro features in Swift by kccqzy on Sunday November 11, 2018 @06:59PM (#18429553)
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.

Re:Building iPad Pro features in Swift by saagarjha on Sunday November 11, 2018 @07:11PM (#18429603)
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.
Re:Building iPad Pro features in Swift by binomialxenon on Sunday November 11, 2018 @11:24PM (#18430575)
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?
Re:Building iPad Pro features in Swift by saagarjha on Monday November 12, 2018 @12:03AM (#18430702)
It's thin, light, and has better specs than my laptop?