This comment is bizarrely antagonistic for no reason and I would appreciate if you'd knock it off. I literally admitted I was incorrect in thinking that I could comfortably write code on my iPad, a point that largely agrees with what you're saying, but for some reason you still feel the need to argue even further.
It should be immediately apparent to most people that I made my decision based on my own personal context and requirements at the time, just as you made your decision in your own context, which is why we each came to a different conclusion. I already made it clear the iPad was only intended to supplement my laptop, not replace it, so obviously I didn't expect it to fully replace my development workflow either. I just thought it might be usable for casual coding when I wasn't at my desk, and I was willing to accept that I might be wrong in that.
There's no point in trying to convince me now that the iPad dev experience sucks, because obviously I already know that, as evidenced by the fact that I literally said it two comments ago (and because you're wrong about why it sucks). You don't win anything for proving I was wrong again.
What I really don't get is why you feel the need to tell me I'm wrong about what the iPad is capable of when I actually bought one and wrote a decent amount of code on it, while you admit you dismissed it as an option with a few minutes of consideration. I have literally written, run, and compiled code on my iPad both locally and remotely using the dev tools you claim don't exist or don't count or are too janky or whatever. What is the point in arguing with me about that when we both already agree it's probably not worth programming on an iPad either way?
The funny thing is that tooling wasn't even the main reason I moved away from coding on my iPad. The tooling wasn't my favorite, but it does exist and was passable for my limited requirements. I just didn't like iPadOS's mediocre multitasking and weird conflicts with key bindings in browser-based dev tools. Were it not for that, I probably would've kept programming on my iPad for a while longer.
It’s not weirdly antagonistic to point out that you’re making factually incorrect claims. Out of all the tooling that goes into a typical developer workflow, iPadOS will only allow you to install a text editor, a web browser, and provides a somewhat restricted filesystem.
You and I might also agree that a shovel isn’t a very good tool for cutting down trees. But this isn’t a conclusion that takes more than a moments consideration to get to.
The only factually incorrect claims here have come from you.
You claimed that the iPad lacks "any developer tools". That's factually incorrect, as you've admitted and repeatedly tried to walk back.
Because you're determined to be right, after you admitted that the iPad has at least some development tools, you tried to move the goalposts and say that the iPad doesn't have any IDEs, while in the same sentence admitting that it has text editors and cloud-based IDEs, which are developer tools. Now you're trying to walk that back again. If you're going to be wrong, you could at least have the decency to be consistently wrong instead of waffling back and forth like this.
You said, "There's also no way to install a runtime or compiler on iPadOS." That's also factually incorrect. I can use basically any compiler or runtime that I want inside iSH without even needing an internet connection after they're installed.
At any rate, I've already explained why none of this is even relevant to the point at hand, but since you can't be wrong, you'll probably ignore these points like you've ignored everything else. Or maybe you're just trolling, who knows? Either way it's pretty pathetic.
It should be immediately apparent to most people that I made my decision based on my own personal context and requirements at the time, just as you made your decision in your own context, which is why we each came to a different conclusion. I already made it clear the iPad was only intended to supplement my laptop, not replace it, so obviously I didn't expect it to fully replace my development workflow either. I just thought it might be usable for casual coding when I wasn't at my desk, and I was willing to accept that I might be wrong in that.
There's no point in trying to convince me now that the iPad dev experience sucks, because obviously I already know that, as evidenced by the fact that I literally said it two comments ago (and because you're wrong about why it sucks). You don't win anything for proving I was wrong again.
What I really don't get is why you feel the need to tell me I'm wrong about what the iPad is capable of when I actually bought one and wrote a decent amount of code on it, while you admit you dismissed it as an option with a few minutes of consideration. I have literally written, run, and compiled code on my iPad both locally and remotely using the dev tools you claim don't exist or don't count or are too janky or whatever. What is the point in arguing with me about that when we both already agree it's probably not worth programming on an iPad either way?
The funny thing is that tooling wasn't even the main reason I moved away from coding on my iPad. The tooling wasn't my favorite, but it does exist and was passable for my limited requirements. I just didn't like iPadOS's mediocre multitasking and weird conflicts with key bindings in browser-based dev tools. Were it not for that, I probably would've kept programming on my iPad for a while longer.