This is the solution being applied before the problem again. It is a case of applying compromises to fit the solution into the available device rather than look at the problem and choose a device suitable for it. I travel with my iPad. It's fine for that. But I'm certainly not going to be writing up anything extensive or writing any code on it.
> I often take on the extra size an iPad may have for size versatility down the road. One doesn’t always have or want to figure out a flat surface to place your device when on the road, in bed, on toilet, or in a bath.
I prefer not to shit or wash where I compute :). As for the surfaces, the iPad is the least flexible device. At worst you have to hold it constantly which is painful after an hour or so.
> I also code quite a lot on my iPad as an iOS dev, because playgrounds are a fantastic way to create mini libraries, apps, or explore some idea you may have on the go. Performance is amazing with the M1 series as well.
Having used Swift Playground extensively, I think you must be living in the future where they fixed all the show stopping bugs and crashes. It's totally unusable for me and doesn't meet even a minimum bar for quality.
>The one thing I dont do with my iPad is any sort of pen input. I’ve never found it useful, but I’m also faster at typing than drawing or annotating. I used to always by the pencil to go with the pro, but stopped doing that a couple years ago because I simply never use it.
It's definitely quicker to type. But it's quicker to draw than type if the scenario isn't suited to textual description.
