4 ms·
Fortunately this tutorial is very high-level and assumes you know another high-level programming language, which allows it to keep a quick pace, preventing it f
by sdegutis 13y ago
Fortunately this tutorial is very high-level and assumes you know another high-level programming language, which allows it to keep a quick pace, preventing it from getting too dry or slow.
I submitted it because I read it last night after starting a new C# project, and was quite surprised to see that it wasn't just a strict subset of C like Objective-C is, but it's a whole language of its own, with some additions and changes that I really really like (especially coming from ObjC).
And yes, C# is only really practical for Microsoft's platforms. But the same could be said about Objective-C and Apple's platforms, and yet we don't mind that. Let's not be inconsistent with our biases.
- deleted 13y ago[deleted]
- gregschlom 13y ago> C# is only really practical for Microsoft's platforms. Not necessarily. If you're doing game development with Unity3D, for example, you're probably going to write much of your game in C#, and it's going to run on Windows, Linux, OS X, Android and iOS.
- randyrand 13y agoHow does Unity3D get C# to run on all those platforms?
- srean 13y agoWish it was true. It has never been true and it is unlikely to be true in near future. Try some non toy F# on windows and on Mono and you will know. Mono leaks, and if you rely on correct behavior of tail calls, you are in for a lot of grief.
- neverminder 13y ago> C# is only really practical for Microsoft's platforms Couldn't agree more with that. This is the reason I stick with JVM based languages (Scala, Java) for high level stuff, C/C++ for low level stuff and naturally JavaScript for browser stuff. This pretty much covers everything and at the same time is unbeatable in performance.