Even the whole non-standard UI argument, which of course is targeted at Flash, doesn't really hold water. Even using Apple's own tools and just the native iPhone API you could create a monster of a UI – or in the case of something like Convertbot a beautiful one, which doesn't even come close to the native look-and-feel of the platform.

As in all trades you're always going to get skilled people and people who can hack stuff together. A crap app is a crap app no matter what language or toolset it's written with.

If MT allows developers to be more productive in producing iPhone apps then surely that can only be a good thing?

This might upset the objective-C camp, but I get the impression the developers using Monotouch are a lot more experienced [enterprise] programmers than the majority of objective-C programmers, and are fluent in more than 1 language. So Steve's statement is really a load of bollocks. Though I can't vouch for Actionscript programmers which he may have been aiming at, and Monotouch gets bundled with

But locking handcuffs on your wrists is exactly what Apple wants. Their new EULA is about control and about locking developers exclusively into Apple's platform. They do not want you have the Freedom of choice. Apple's whole product philosophy since the release of the original Mac in 1984 has always been about removing choice, not giving it.

The new EULA tries to fix holes in their walled garden before they even become real holes. Every development tool that does not come from Apple might become a multi-platform tool one day that could allow developers to easily port their apps to a competitior's platform. MonoTouch will soon be released for Android. Do you honestly believe that Apple will make a EULA exception for MonoTouch? Certainly not. Unity for the iPhone will also be banned, and if RealBASIC for the iPhone ever came out, it would be banned, too.

Apple will not take back that new EULA. It's not (yet) in their interest. Should the day come that they have lost too much market share to Android, they might rudder back. But until then… No chance.

One common argument is that if Novell stopped supporting MonoTouch, it would put developers at risk, and (somehow) put Apple in a situation such as the 'Metrowerks PowerPlant framework).

Since we can actually bind API's ourselves with btouch for MonoTouch, if Novell dropped support, we could still access any new API's that apple released, either by someone picking up the slack and releasing it to the public, or by each developer coding the calls to new API's themselves.

The rest of the post is spot on, I just wanted to add this as a counter-argument to one point that some folks are stuck on (*cough* Gruber).

MonoTouch is a fantastic tool, and I see no legitimate reason for it to be silenced from the AppStore. Kudos for Diggify, let's keep MonoTouch apps coming

pageControl.ValueChanged += delegate(object sender, EventArgs e) {
var pc = (UIPageControl)sender;
double fromPage = Math.Floor((scrollView.ContentOffset.X – scrollView.Frame.Width / 2) / scrollView.Frame.Width) + 1;
var toPage = pc.CurrentPage;
var pageOffset = scrollView.Frame.Width*toPage;
Console.WriteLine("fromPage " + fromPage + " toPage " + toPage);
PointF p = new PointF(pageOffset, 0);
scrollView.SetContentOffset(p,true);
};