iPhone development emergency guide • Hacker News Board

Re: iPhone development emergency guide

#21

Post by xel02 » Wed, Jul 22, 2009, 7:19 PM UTC

jcl wrote: post #20

dejb wrote: post #18

Earlier quoted context omitted.

That would truly be a sad future, worse than the '1984' scenario being played out by Amazon's DRM. What free person would want to rely on a device that required the manufacturers constant consent to allow it to function as that they wanted? Thankfully this seems unlikely. History suggests that there is a significant benefit in choice and freedom and that consumers will eventually follow that path. > It's easier for t…

The important thing is not the lock-in, and probably not even the pre-screening of applications. The important thing is the streamlining of getting software and updates to the user. If centralized software distribution scares you, be afraid of Ubuntu.

With the iPhone there is one software repository. With Ubuntu (and most major distributions) you can roll your own repository (or someone selling software can).

Centralized software distribution is awesome, the issue with the iPhone model is that you have to be anointed.

Re: iPhone development emergency guide

#22

Post by Morn » Wed, Jul 22, 2009, 11:25 PM UTC

jsonscripter wrote: post #19

jlongster wrote: post #15

Earlier quoted context omitted.

You don't have to use Objective-C, and you are free to use a language with a garbage collector: http://jlongster.com/blog/2009/06/17/write-apps-iphone-schem...

You still have to have C in the end. The license agreement forces it upon you. That's disgusting.

That's not true. You can use any language/compiler combination that will compile to an ARM binary. See, for example, ArsTechnica's roundup of the state of C#/Mono on the iPhone: http://arstechnica.com/open-source/news/2009/01/open-source-...

Re: iPhone development emergency guide

#23

Post by dejb » Thu, Jul 23, 2009, 2:59 AM UTC

jcl wrote: post #20

dejb wrote: post #18

Earlier quoted context omitted.

That would truly be a sad future, worse than the '1984' scenario being played out by Amazon's DRM. What free person would want to rely on a device that required the manufacturers constant consent to allow it to function as that they wanted? Thankfully this seems unlikely. History suggests that there is a significant benefit in choice and freedom and that consumers will eventually follow that path. > It's easier for t…

The important thing is not the lock-in, and probably not even the pre-screening of applications. The important thing is the streamlining of getting software and updates to the user. If centralized software distribution scares you, be afraid of Ubuntu.

All losses of freedom are important. Ubuntu doesn't force you to use them for software distribution or updates.

Of course Apple could do the same without any loss of experience for those who wanted to stay within their cage. The only possible 'benefit' in enforcing these restrictions is the prevention of pirating of software. But DRM hasn't worked for music and there isn't much reason to think it will work for software either.

Re: iPhone development emergency guide

#24

Post by TJensen » Sat, Jul 25, 2009, 4:08 AM UTC

smikhanov wrote: post #12

TJensen wrote: post #7

Earlier quoted context omitted.

I use Emacs and Make as my IDE (yes, it does call xcode to do the actual compile). There is at least one Ruby and one Javascript compiler you can use.

Could you please give a little bit more info on how do you do this (and links to Ruby/JS compilers)?

This goes in my Makefile. I have to add files in xcode.

  all: 
  	xcodebuild -activeconfiguration -activetarget -sdk iphonesimulator3.0 -project MyProject.xcodeproj

I may have to back out of the Ruby. I thought I remembered reading about a Ruby project for iPhone apps, but I think I was smoking something that day.