4 ms·
Having used the iPad quite a bit, I don't think code editors are the problem when it comes to coding. After all, you can do that in pretty much anything. The b
by Swizec 16y ago
Having used the iPad quite a bit, I don't think code editors are the problem when it comes to coding. After all, you can do that in pretty much anything.
The biggest disadvantage would be the keyboard. Especially how it handles "weird" characters that the average coder needs to be first-level rather than hidden somewhere deep.
Here's a good idea on how the keyboard could be greatly improved -> http://rosscarter.com/2010/320.html http://rosscarter.com/2010/320.html
- pornel 16y agoA fixed layout of a virtual keyboard is a silly problem created by Apple — keyboard customization is a private API. Hopefully the restriction will be relaxed in future versions of iOS.
- jforman 16y agoI wouldn't call enforcing consistency in a primary interaction mode "silly." There would be a considerable increase in cognitive load if a user had to parse what they're seeing every time a keyboard appears. You'd benefit the tail (e.g., people who want to code on an iPad) but reduce utility for the majority of users. Like most things, it's a trade-off, and Apple usually (almost always?) lands on the side of simplicity in that trade-off.
- pornel 16y agoThey did it successfully for Numbers.app. All applications are curated, so they could add "Confusing keyboard" to long list of rejections.