[czx4f4bd]

My use case didn't require an IDE. My main intent was to remote into my batteryless laptop, so in principle the iPad didn't need much functionality of its own.

That said, I don't know what you mean by "the lack of any developer tools". There are absolutely code editors, IDEs, SSH clients, and even runtimes for iPadOS. There are also lots of web-based IDEs and editors now, even self-hostable ones like code-server. Obviously I wouldn't have bought mine if those didn't exist.

[AmericanChopper]

There are no IDEs that run on iPadOS, the best you can get is either a text editor with basic high lighting, or a “cloud” IDE. There’s also no way to install a runtime or compiler on iPadOS. Unless you’re already using some cloud based solution (in which case you should already be familiar with their pitfalls), it should be immediately apparent to most developers that their workflows aren’t going to run on an iPad. It doesn’t have the most basic tools that you would need, not even the ability to run the code that you write. People do use it, but the level of jankiness they’re accepting is immediately apparent, even if you’re only consulting the most vocal advocates. I also considered this when I saw how cool the iPad Pro looked, but it barely took more than a couple of minutes to figure out that it wasn’t worth trying.

[czx4f4bd]

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.