I couldn't agree more with this article. I have been an iPad owner since I got the very first iPad on the day it was released and I am owning a 13" iPad Pro for

I couldn't agree more with this article. I have been an iPad owner since I got the very first iPad on the day it was released and I am owning a 13" iPad Pro for 4 years now. I have always considered the iPad as an extremels faszinating hardware experience. But its actual use always seems to be constrained by the software. Indeed, it was always rumored how powerful the processor of the iPad must be, as little things are slow on that machine. But it wasn't widely acknowledged, as very few big software packages are running on the iPad. Count the percentage of software on the Mac which doesn't sell via the App Store and one might get an estimate, what the iPad is missing out. Partially, this has fiscal reasons, avoiding the revenue share with Apple, but a lot has to do with the App Store restrictions. There are far too many applications which are restricted or outrightly banned by the app store. When I started computing, a computer would come with an implementation of basic. You could immediately start programming on that computer. In my case it was the C64, for others MS Basic on DOS. Not even that exists on the iPad. There are a very few IDEs, which constantly have to avoid being too useful to prevent being banned. To big the danger for Apple seems, if you manage to write an useful App on the iPad without going through the App Store. Imagine a full featured Python or just Basic, which allows you to write programs with full screen graphics als full user interaction on the iPad. Imagine, if someone ported Squeak as an iPad app. It could perfectly run the whole environment inside the App, this would be a great experience. Imagine running a Lisp machine as an App. On the technical side, the iPad needs more memory. If it is meant as a "Pro" machine, it should have 8Gb of RAM, optionally 16. But most importantly, a limited form of swap should be introduced. Limiting the active memory of a single app to the available system memory makes sense, but the more complex an application becomes, the less it is acceptable to kill the process just because the user switches to another App. Even on the fastest machine, restoring the state might not be possible fast enough. This can eliminate a wide range of application. Instead, deactivated applications should be swapped out. So the swap would just allow them to run without interruptions.