Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>My hunch is that the companies you talked to simply are used to using Objective-C. That's where their skills lie, and that's the biggest reason why they would prefer not to deviate from their path. The other reasons can be argued both ways.</p> <p>It's true that no one can predict what Apple will do, but there's a <em>very</em> small likelihood that Apple will ban third-party toolkits &amp; APIs like they did in the summer of 2010. That was only a short period of time, and they completely reversed that decision. Their current focus is on making app development easier, which means keeping the field open to alternative development methods. I think MonoTouch is safe.</p> <p>As for speed, C# generally produces very fast executables. They may not be <em>quite</em> as fast as Objective-C, but I doubt you'd notice a difference. I remember seeing a website somewhere that showed C# outperforming C/C++ in some tests, but that was in the .NET environment, not Mono... and unfortunately I can't find the reference anymore. I'll keep looking. But the bottom line on speed is that C# speeds are very good. It's not like BASIC vs C. More like Java/JIT vs C.</p> <p>C# gives you many, <em>many(!)</em> advantages over Objective-C, and they have been enumerated in other Stack Overflow answers, so I won't repeat them here. You can find them easily enough.</p> <p>I'm an obvious fan of MonoTouch, but I do have to say one thing: I think it's a mistake for companies to think that because they are fluent in C#/.NET that they will easily be able to develop and/or maintain iOS apps using MonoTouch. It's just not true, because MonoTouch is basically a C# layer over the CocoaTouch API, meaning that you have to learn the Apple way of doing things. You have app delegates and view controllers and all the UIKit stuff. There's a real learning curve there. But if you're fluent in C#, MonoTouch will be a huge help.</p> <p><strong>UPDATE:</strong><br/> I found the article on C# speed: <a href="http://www.codeproject.com/Articles/212856/Head-to-head-benchmark-Csharp-vs-NET" rel="noreferrer">Head-to-head benchmark: C++ vs .NET</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload