4 ms·
I know I'm not the target user for the product but not being able to write code on it is a pretty significant functional setback.
by OhSoHumble 6y ago
I know I'm not the target user for the product but not being able to write code on it is a pretty significant functional setback.
- Jtsummers 6y agoThe bigger issue isn’t writing code (that’s feasible, as is using git), it’s building code. You need a server to load it to or a build pipeline setup for the repository.
- Operyl 6y agoI can write code with it, and execute on it in some cases. For example, I find myself using Swift Playground to quickly test out some code I’m tinkering with and run it on device. Or Pythonista/the other interpreters on the App Store. Or I use Blink to SSH into a VM where I can write code to run on Linux etc. I use it quite often.
- Koshkin 6y agohttps://medium.com/@igorandreev/how-to-code-with-ipad-pro-make-your-2019-year-of-mobile-development-e4e678daab77 https://medium.com/@igorandreev/how-to-code-with-ipad-pro-ma...
- rowanG077 6y agoI don't think this qualifies. You have to use bespoke tools end environments to be able to code in a very limited fashion.
- shmoogy 6y agoI think a lot of people can get by just fine with SSH/mosh, vim, tmux... I did this for a bit but actually run vs code-server a lot too.
- rowanG077 6y agoThat setup requires you to always have internet. It also requires you to have a remote PC somewhere where you develop. The Ipad is little more then a screen in that case. In contrast I use a Surface Pro and I don't even have a desktop PC. That's the difference between these devices. One is a fully fledged computer where you can do whatever you want on it. The other is a glorified teletype terminal. It's fine that the iPad Pro isn't a fully functional computing device but the thing that is wrong is Apply positioning it as such.
- walterbell 6y agoXcode is rumored to arrive on iPad this year.
- theshadowknows 6y agoSir you’ve given me a reason to live.
- Operyl 6y agoAs much as I want this rumor to be true, the leaker that “leaked” this has a terrible track record. Furthermore, what he “leaked” is something already in iOS 13 thats meant to be a companion app to Xcode for some debugging stuff.