Well, I might say it's not fair because iSH is not your only choice on the iPhone, at least if your goal is "checking out a git repo and editing files." Running git clone using an actual iOS native git client like Working Copy is pretty fast. And because Working Copy is an iOS file provider, you can edit files in a repo directly in a native iOS text editor like Textastic. If we're talking about doing web development, pair that with a cheap Linode or Digital Ocean VPS, the Blink terminal app and/or Secure ShellFish (an SSH client that also hooks in SFTP/SCP in as a file provider along with Shortcuts automation) and you're probably doing pretty darn well.
Now, if your goal is "do dev work just the same way I would on a Mac or a Linux machine," then no, the iPad's not going to cut it in its current incarnation, for reasons which one can argue are arbitrary. But honestly, I don't think a PinePhone will really cut it, either. :)
(Digression on arbitrariness: Apple has so far stuck very doggedly to the notion that iPads, like iPhones, should be more like consoles than general purpose computers, and their decisions about the platform mostly make sense if you look at them from that "app console" perspective. That doesn't mean they're the right decisions, but they're definitely conscious decisions. Up until, well, today I was pretty sure Apple was going to keep sticking by this, and that their response to people saying "what about Xcode on the iPad" would be "may we interest you in this Apple Silicon-based Macbook". Putting the M1 CPU in the new iPad Pro under the M1 branding, rather than calling it "A14X" or some such, give me some pause, though.)
As a heavy Working Copy user, with all the respect I have for its great developer, it is just a bad UX; Buggy, slow as hell, and you need to constantly wait for it as you can't minimize the app as the dumb iOS will kill it.
SSH via Blink is also not a very good experience (the keyboard is buggy), but it's good enough. The problem is when you want to do some local stuff, e.g., play some multimedia file, or do some expensive computation that your server is too weak to do. Only a fool pays +1000$ for a dumb terminal. (Of course, artists have their apps, and they are the sole group who are served by the iPad Pro.)
I'm not a huge fan of Working Copy's UI, although to be fair to it, I find a lot of desktop GUI Git clients to be pretty arcane as well. My experience with Blink has been pretty good on the whole, though. In any case, I was focusing on iSH specifically -- I'm just not convinced that "when I run this terminal program which is a clever hack to allow console Linux apps to run in x86 emulation, it's a poor experience" is a great argument against the iPad's utility. :)
But, I'll take gentle issue with
> the sole group who are served by the iPad Pro
I also know or know of writers, photographers, DJs, musicians, and podcasters who do a lot of work on iPads. It was my only portable computer for over a year, and the one I took with me on sometimes long trips. I got real, genuine work done on it, and I am not an artist. I have my complaints with it, to be sure (you might notice I'm using past tense there). But I think the HN audience has a bias toward "ease of use as a development platform" as a primary measure of utility -- which happens to be a measure that the iPad does very poorly on. That's an understandable bias given that audience, but it's worth poking around and seeing what "iPad first" power users are actually doing with their iPads even with the occasionally maddening limitations baked into iPadOS.
Now, if your goal is "do dev work just the same way I would on a Mac or a Linux machine," then no, the iPad's not going to cut it in its current incarnation, for reasons which one can argue are arbitrary. But honestly, I don't think a PinePhone will really cut it, either. :)
(Digression on arbitrariness: Apple has so far stuck very doggedly to the notion that iPads, like iPhones, should be more like consoles than general purpose computers, and their decisions about the platform mostly make sense if you look at them from that "app console" perspective. That doesn't mean they're the right decisions, but they're definitely conscious decisions. Up until, well, today I was pretty sure Apple was going to keep sticking by this, and that their response to people saying "what about Xcode on the iPad" would be "may we interest you in this Apple Silicon-based Macbook". Putting the M1 CPU in the new iPad Pro under the M1 branding, rather than calling it "A14X" or some such, give me some pause, though.)