To view parent comment, click here.
To read all comments associated with this story, please click here.
There was only one jailbreak that didn't require a PC, and it worked on only two minor revisions of iOS 4. All other jailbreaks required a PC to develop and a PC for the actual jailbreaking.
Also, what I meant by practical, is you're not going to sit and develop on a smartphone or iPad for 6 hours straight without causing some serious hand fatigue. Also, you're not going to have simultaneous access to your debugging tools, or other things you might require when building your software. While it is handy for on-the-spot development of smaller solutions, you aren't going to be doing any large tasks on such a limited device.
You can't define things that are variable over time and include them in a classification system, unless you want to update the classifications every couple of months. That would render it pretty much worthless as you'd have to make a note of what the definitions were back when some one cited a statistic that used the definition.
All of your classifications are so dependent on things that could change tomorrow. If you can develop on the device.... If you can perform action A on it without the use of another device... Its like piece wise defining a sine wave... There is probably a better way to do it without having so many conditions to examine. I don't mean to knock down everything you are suggesting, but I think you need to zoom out and take a wider look at the situation as others seem to be on a more sensible track.




Member since:
2006-07-14
Point 1: Jail breaking does not require a PC. There was a website that did it automatically. its just an exploit in the OS, which can be triggered remotely as well as locally under the right circumstances.
Point 2: Android tablets like the Galaxy I referenced. No PC required, programming pretty easy with python. Does that mean Android tablets are PCs and Ipads are not? I think the first replier had it right. You can't define "PC" that way.
Aside: I'm also not entirely comfortable with the "practical" part of your argument. What kind of development is practical and what is not? I know many people that would argue that programming in assembler is not "practical", while others would say that about Java, or Perl, or Visual Basic, Or C#, or C, Or Python, Or PHP, or Brain Fudge, or Haskell, Or Action script, or Ruby. Its too much of a personal taste/ judgement call thing.