News for hackers. Stuff that matters.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by edster on Thursday April 08, 2010 @07:07PM (#1251338)
It's not just with the consoles. I used to develop Lotus Notes applications. The problem with Notes was that the barrier to entry for developers was too low such that it hurt the platform, and it made it hard to distinguish good developers and good apps from the chaff. When a bunch of unqualified developers fill the world with junk it gives the entire platform a reputation as being junky.

I now develop iPhone applications, and I personally agree with Apple in this respect. If you want to develop iPhone applications, spend some time and become proficient with the tools.

And, @raganwald is correct that it's still lock-in, it's just a matter of where the lock is.

Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by fauigerzigerk on Friday April 09, 2010 @02:34AM (#1252060)
Your lock-in argument is wrong. Of course there are always dependencies. But it's important to be able to choose which dependencies are the right ones for your application. Mandating a particular API isn't just lock-in. It's lock-in lock-in. You're signing away the right to choose the right tool for the job.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by mkramlich on Friday April 09, 2010 @03:22AM (#1252125)
Apple should filter by quality, not by what language/technology was used to make the app.

It makes more sense to reject Fart apps -- or least the 100th Fart app. It does not make sense to reject apps written in Python or Clojure, for example.

To put it another way: they are disproportionately turning away the better quality devs, not the lower quality ones.

Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others by lolindian on Friday April 09, 2010 @05:40AM (#1252287)
Democracy is similar. I used to have a nice life as a french king, until the stupid peasants took over. Now everything is fucked. I feel so locked in.