MonoTouch for iPhone - C# bindings for native APIs • Hacker News Board

Re: MonoTouch for iPhone - C# bindings for native APIs

#21

Post by ryanpetrich » Tue, Sep 15, 2009, 5:15 AM UTC

rufugee wrote: post #19

antonovka wrote: post #17

Earlier quoted context omitted.

Not being able to measure on-device performance and stability during evaluation is a pretty big deal. The simulator is only useful as a smoke test, even when using the native tools.

Actually, that's a very good point. I guess my wish is that one could deploy to a device, but not actually upload to the appstore or sell without a license. Testing on a device is absolutely crucial...

Perhaps a mandatory nag screen at startup for binaries generated with the evaluation edition?

Re: MonoTouch for iPhone - C# bindings for native APIs

#22

Post by jasonkester » Tue, Sep 15, 2009, 8:28 AM UTC

solutionyogi wrote: post #20

jasonkester wrote: post #2

It looks like you have to develop in MonoDevelop to use this, which is a bit of a shame. After all, the reason most teams use C# in the first place is that you get to use the best IDE around. Outside the context of VS.NET, C# doesn't have nearly as much going for it. Still, if it lets me avoid Objective C, I think I'll give this a shot.

Jason, I have a lot of respect for you but saying that C# doesn't have anything going other than the IDE is completely wrong. With LINQ, lambda expressions, continuations, reflection, extension methods, automatic properties, I believe that C# is the no.1 strongly typed language.

I also believe that C# is the #1 strongly typed language, and it's my language of choice for pretty much all of my own projects. Sorry if I implied otherwise (and therefore tarnished my reputation as a fanatical microsoft supporter).

There is actually a hole in the other half of my earlier statement. Java has essentially the same quality IDE available (since IntelliJ IDEA =~ VS.NET + ReSharper), and yet I don't find myself compelled to use it for anything.

Re: MonoTouch for iPhone - C# bindings for native APIs

#23

Post by jcl » Tue, Sep 15, 2009, 3:39 PM UTC

ryanpetrich wrote: post #21

rufugee wrote: post #19

Earlier quoted context omitted.

Actually, that's a very good point. I guess my wish is that one could deploy to a device, but not actually upload to the appstore or sell without a license. Testing on a device is absolutely crucial...

Perhaps a mandatory nag screen at startup for binaries generated with the evaluation edition?

Or perhaps display a page from the Kama Sutra? That ought to keep it out of the App Store. :)