Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COFirst off, C# is *not* a "domain specific language" - far from it. It's a commodity skill. That's part of the value of MonoTouch. It could be argued (unfairly and inaccurately) that ObjC is a DSL in that most devs (outside finance and university labs and basements) will only ever use it for OS X or iPhone development. But it isn't. Like C#, it's a versatile language that basically exists to let you focus on frameworks rather than the language itself (I think we agree there). But keep in mind that your *ObjC* code will break with Apple updates. That's not an MT specific issue.
      singulars
    2. COMT could even save you in some cases *because* there's this layer of abstraction. Apple modifies an API? Well, your ObjC app *and* your (let's pretend it exists) equivalent MT app will break. The MT guys could release a stopgap solution to modify how the MonoTouch API handles the call behind the scenes. Your MT code wouldn't have to change - you could just rebuild against the stopgap MT release. Yes: this is a *dirty* fix that could easily lead to problems, but properly deprecating the stopgap MT API would give devs time to handle the change seamlessly *and* buy time for a *real* fix.
      singulars
    3. COPlus, new as MT is, it just got a lot easier to create your own bindings if necessary (MT 1.2). You're not completely dependent on the MT peeps to do all that work (though they *are* doing that work), and never were. They have dead-simple ways of creating bindings. They expose enough of the ObjC runtime with the MT frameworks that you're not locked into their way of doing things. I've reimplemented bindings just to see if I like my way better. You can ignore the MT frameworks and send and receive messages "manually" if you want, and it takes little code. They're smart people. Trust them :)
      singulars
 

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