 |
 |
Any one use Mac for C# programming?
|
|
|
|
|
Dedicated MacNNer
Join Date: Aug 2004
Status:
Offline
|
|
is that possible on a Mac?
how important is C# among software develop industry?Worth learning?Advantage over java or other programming language?
thx in advance
|
|
There were once four people named Everybody, Somebody, Nobody and Anybody. Somebody had to do a job, but Nobody wanted to do it. Nobody could see that Anybody could do it, and Somebody got angry about that because it was Everybody's job. Nobody ended up doing it, and it so happened that Everybody blamed Somebody when Nobody did what Anybody could have done.
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: May 2001
Location: ~/
Status:
Offline
|
|
It's entirely possible to write and run C# applications on OSX. One part of the Mono project is Cocoa# which are C# bindings to Cocoa which lets you write native OSX applications in C# instead of Objective-C or another Cocoa supporting language. This is beneficial because you can take your C# know-how and use it right away on OSX. The downside is a majority of C# programming is done inside of the .NET framework. Even projects compatible with Mono are still using the .NET API. If you spend all your time within the .NET API you're going to relearn the Cocoa way of doing everything. You can port a Windows.Forms application to OSX using macpack with the MonoFramework but you're limited to the capabilities of the MWF portion of the Mono project which is roughly 90% of the full specification.
Pros: Learning C# will help you better understand programming on different platforms and thanks to the Mono guys you can write applications that will run passably on Windows, Linux, and Mac. It is entirely possible to write Cocoa applications in C#. C# is very similar in feel to Java so if you've studied Java you'll be very comfortable in C#.
Cons: C# is not a first class language on Mac or Linux systems and the .NET runtime environment still isn't prevalent on Windows. There's a lot of hype surrounding it, mostly by MSDN Magazine and other Windows development rags. Its real-world usage is far below that of C++, Java, or VB6. On the Mac Objective-C, Java, and scripting languages like Perl, Python, and Ruby have far more (not necessarily better) support than C#.
|
|
|
| |
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Aug 2004
Status:
Offline
|
|
Originally Posted by Graymalkin
It's entirely possible to write and run C# applications on OSX. One part of the Mono project is Cocoa# which are C# bindings to Cocoa which lets you write native OSX applications in C# instead of Objective-C or another Cocoa supporting language. This is beneficial because you can take your C# know-how and use it right away on OSX. The downside is a majority of C# programming is done inside of the .NET framework. Even projects compatible with Mono are still using the .NET API. If you spend all your time within the .NET API you're going to relearn the Cocoa way of doing everything. You can port a Windows.Forms application to OSX using macpack with the MonoFramework but you're limited to the capabilities of the MWF portion of the Mono project which is roughly 90% of the full specification.
Pros: Learning C# will help you better understand programming on different platforms and thanks to the Mono guys you can write applications that will run passably on Windows, Linux, and Mac. It is entirely possible to write Cocoa applications in C#. C# is very similar in feel to Java so if you've studied Java you'll be very comfortable in C#.
Cons: C# is not a first class language on Mac or Linux systems and the .NET runtime environment still isn't prevalent on Windows. There's a lot of hype surrounding it, mostly by MSDN Magazine and other Windows development rags. Its real-world usage is far below that of C++, Java, or VB6. On the Mac Objective-C, Java, and scripting languages like Perl, Python, and Ruby have far more (not necessarily better) support than C#.
thanks for that replay,really appreciate
|
|
There were once four people named Everybody, Somebody, Nobody and Anybody. Somebody had to do a job, but Nobody wanted to do it. Nobody could see that Anybody could do it, and Somebody got angry about that because it was Everybody's job. Nobody ended up doing it, and it so happened that Everybody blamed Somebody when Nobody did what Anybody could have done.
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: May 2001
Location: ~/
Status:
Offline
|
|
No problem man, it forced me to look up some stuff on Cocoa# that someone else had asked me about a few days ago. I was able to kill two birds with one stone. 
|
|
|
| |
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Aug 2004
Status:
Offline
|
|
|
|
|
There were once four people named Everybody, Somebody, Nobody and Anybody. Somebody had to do a job, but Nobody wanted to do it. Nobody could see that Anybody could do it, and Somebody got angry about that because it was Everybody's job. Nobody ended up doing it, and it so happened that Everybody blamed Somebody when Nobody did what Anybody could have done.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
Top