A Computer for Everything: One Year of iPad Pro

Re:A Computer for Everything: One Year of iPad Pro by falcolas on Saturday December 17, 2016 @11:45AM (#13201305)

The same way he did Python, in a console. The only languages which may be a challenge to program in that fashion would be Swift, Objective C, and C# - because they are so tied to MacOS and Windows respectively.

A well set up Vim or Emacs is perfectly capable of writing Node.js, Java, C (side note - hilarious that you tried to use this as an example, given that C and C++ are probably written by a majority of developers in the console) and Go.

[ Parent | on HN ]

Re:A Computer for Everything: One Year of iPad Pro by wslh on Saturday December 17, 2016 @01:47PM (#13201825)

Developing using a remote computer is not developing in the iPad itself.

[ Parent | on HN ]

Re:A Computer for Everything: One Year of iPad Pro by whiskers on Saturday December 17, 2016 @03:48PM (#13202482)

The point is that it's an equivalent workflow. It doesn't make the process of developing worse if you're used to those tools so why does it matter if it's 100% local?

We can assume if it's working for them then network connectivity isn't an issue (which is isn't for most of us, most of the time).

[ Parent | on HN ]

Re:A Computer for Everything: One Year of iPad Pro by caconym_ on Saturday December 17, 2016 @10:28PM (#13204154)

Since we're talking about the feasibility of using an iPad for software development, this seems like irrelevant semantics.

[ Parent | on HN ]