Live data from Hacker News

Buying an iPad Pro for coding was a mistake

technicallychallenged.substack.com

11–20 of 533 posts

Re: Buying an iPad Pro for coding was a mistake

#11

you can't code on iOS why would even attempt this lmao. this isn't the thing they try to sell you on, its other kinds of apps and professions not engineering xcode for ipad is on the horizon but I ain't holding my breath, they took years to implement something similar to Samsung DeX and even then its really poorly implemented and doesn't work well. (not to mention it isn't rolled out to all ipads)

hosted vscode, github codespaces etc - coding on ipad is very much possible.

Re: Buying an iPad Pro for coding was a mistake

#12

It's "possible" to code now with GitHub Codespaces, which leverages VS Code for Web and has pretty good usability on the iPad, and there are a few less-conveinent ways to run the VS Code Web interface hosted on your own computer (e.g. Blink Shell: https://docs.blink.sh/advanced/code )

by this definition a chromebook is an excellent programming machine

Yes? It's 2023, not all code has to be run locally.

Re: Buying an iPad Pro for coding was a mistake

#13
post #11

you can't code on iOS why would even attempt this lmao. this isn't the thing they try to sell you on, its other kinds of apps and professions not engineering xcode for ipad is on the horizon but I ain't holding my breath, they took years to implement something similar to Samsung DeX and even then its really poorly implemented and doesn't work well. (not to mention it isn't rolled out to all ipads)

hosted vscode, github codespaces etc - coding on ipad is very much possible.

"you can visit a website"

okay my smart toaster is an excellent dev machine as well

I'm looking for something like swift playgrounds++ so baby xcode, not a remote window

Re: Buying an iPad Pro for coding was a mistake

#14
I’ve owned ipads for a long time and their productivity benefits compared to my Mac and iphone has never improved over the years. This year I’m selling my last ipad and won’t buy again until Apple throws a “real” OS at the thing.

one of the worst things about ios is that files get copied for each app. Say I download a PDF in the Documents app and want to annotate it. As soon as I open it with NoteX, a copy of the PDF is created in NoteX folder. this results in a chaotic situation, in terms of files and hierarchies.

Re: Buying an iPad Pro for coding was a mistake

#15

I have the iPad Air with the same M1 chip and it’s such a disappointment for this exact reason. It literally has the same SoC as my MacBook, but is basically useless for most productive activities I’d like to do with it. (And even goes slower at the tasks it can do!) It really highlights just how awful iPadOS is compared to MacOS.

they are so close to unlocking iPad and iPhone's potential but sadly keep doubling down on the locked experience. even the vision pro, seem really disappointing that its essentially running iPadOS with ARKit

Exactly! That strikes me as the biggest problem with the Vision Pro that is consistently overlooked: by running what appears to be an iPadOS derivative, its usefulness will be mostly limited to web browsing with Safari.

Being able to code in multiple VR monitors while traveling actually sounds like a good potential use case that Apple has locked themselves out of with their crippled OS.

Re: Buying an iPad Pro for coding was a mistake

#16

Earlier quoted context omitted.

by this definition a chromebook is an excellent programming machine

Yes? It's 2023, not all code has to be run locally.

I think you may be missing the point of the criticism.

its obvious that remotely editing code is possible, but why would you spend so much money on something that is basically a remote desktop machine?

couldn't you use a much cheaper device for the same purpose

Re: Buying an iPad Pro for coding was a mistake

#17

An ipad to be used with an external keyboard is a very suboptimal typing experience - there is usually no strong hinge to hold up the screen at arbitrary angles. In my experience this also means you can't 'pick up' the system by the keyboard to move it around (which I do with my laptop all the time) so it feels super-awkward. For drawing with the pencil, sure it's a great experience but if you need to output a ton of…

The Magic Keyboard does solve these concerns (although you should probably wait for a sale)

Re: Buying an iPad Pro for coding was a mistake

#18

It's "possible" to code now with GitHub Codespaces, which leverages VS Code for Web and has pretty good usability on the iPad, and there are a few less-conveinent ways to run the VS Code Web interface hosted on your own computer (e.g. Blink Shell: https://docs.blink.sh/advanced/code )

by this definition a chromebook is an excellent programming machine

I mean, you can run actual Linux applications on those. Only limit is gonna be the mostly crappy hardware. Although I guess that could be to the benefit of everyone actually using your software.

Re: Buying an iPad Pro for coding was a mistake

#19

I’ve owned ipads for a long time and their productivity benefits compared to my Mac and iphone has never improved over the years. This year I’m selling my last ipad and won’t buy again until Apple throws a “real” OS at the thing. one of the worst things about ios is that files get copied for each app. Say I download a PDF in the Documents app and want to annotate it. As soon as I open it with NoteX, a copy of the PDF…

I can't wait for ipads to mature

Re: Buying an iPad Pro for coding was a mistake

#20

Earlier quoted context omitted.

they are so close to unlocking iPad and iPhone's potential but sadly keep doubling down on the locked experience. even the vision pro, seem really disappointing that its essentially running iPadOS with ARKit

Exactly! That strikes me as the biggest problem with the Vision Pro that is consistently overlooked: by running what appears to be an iPadOS derivative, its usefulness will be mostly limited to web browsing with Safari. Being able to code in multiple VR monitors while traveling actually sounds like a good potential use case that Apple has locked themselves out of with their crippled OS.

I'll still just use vscode in multiple windows :)))

you can't stop us all, apple!

Post reply on HN