Apple development (new platform)

Question

Based on Microsoft backgroup development, I'm a little confused as to which languages ​​/ development environments are available on a Mac. Are there any C # languages ​​for Mac development other than Java that I should also consider? What do MS-OSX converters prefer and why? I am following a business-level programming strategy, not games or graphics, so application performance is not a general driver for my platform choice.

Answer 1

Objective-C with the Cocoa API is the way to go. Once you have this, there are also bridges between Ruby and Python in the Cocoa API. At first, I highly recommend learning the Cocoa API with Objective-C first.

Answer 2

I also just bought a Mac and came from a .NET development background. I tried a bunch of different languages ​​and environments. If you are planning to write OS X desktop software, you will need to use Cocoa and Interface Builder. IB has no Windows counterpart because it is so much attached to Cocoa. This means that you will need to learn Cocoa at the same time, and this is not easy to do by looking at the code.

Objective-C - Mac, , #. , , . Python Ruby Objective-C , Cocoa, . # Mono , , Cocoa # . # , Visual Studio, MonoDevelop Mac. , , , Objective-C, .

-, . Python Ruby, Python. , , Python, 100% Linux. iTerm - , . , , Smultron, , . .

, , . Python, , , . SQLAlchemy (Python ORM) . Vim (MacVim ), , , , . (, , $, , , , Enter, , Google , o.)

Answer 3

Mono project

wikipedia

Mono - Novell ( Ximian) Ecma, .NET , , , # - Common Language Runtime. Linux, BSD, UNIX, Mac OS X, Solaris Windows.

Cocoa Aaron Hillegass "Cocoa Mac OS X"

Answer 4

Objective-C, C, ++, Java, Ruby, Python, Php,... / , # Mono, @epatel. , , , , .

Answer 5

Objective-C Cocoa - . , Objective-c "" " ". , . .

Answer 6

Silverlight - -, "flash-like", Windows Mac, .net .

Answer 7

# OS X, Mono. -UI - .

REALbasic. Visual Basic.

- , Cocoa/Objective-C ; .NET / Java.

Answer 8

, . , system.drawing/forms .

With C #, I would go with monomac. You get access to all mac apis, but in C #. It's like a halfway house. Instead of forms, you use NSWindow, and instead of controls, you use NSView. Instead of drawing, you use a graphics context. The downside is that the documentation is a bit thin and worth it.