C# Tutorials
msdn.microsoft.com
C# Tutorials
1–10 of 66 posts
Re: C# Tutorials
#2Operator overloading is super useful - I help maintain FluentCassandra and we overload the implicit conversion operators to make it seamless to convert from built-in .NET types and their associated Cassandra types. It makes a MASSIVE impact on the user experience and amount of boilerplate code it eliminates.
Re: C# Tutorials
#3These feel pretty outdated. C# 2, I believe? It has generics and delegates, but none of the things C# is appreciated for these days, such as LINQ, lambdas, async/await, etc.
Re: C# Tutorials
#4In broad strokes, what are the differences between Java and C# and why should I bother with it?
(Disclosure: I hate Java)
Re: C# Tutorials
#5From a distance, C# looks like an incredibly awesome language, but the way it's tied so closely to Visual Studio and Windows really crimps its growth.
I love it's syntax, the libraries look great, and apparently the performance isn't that bad either.
Re: C# Tutorials
#6In broad strokes, what are the differences between Java and C# and why should I bother with it? (Disclosure: I hate Java)
Re: C# Tutorials
#7From a distance, C# looks like an incredibly awesome language, but the way it's tied so closely to Visual Studio and Windows really crimps its growth. I love it's syntax, the libraries look great, and apparently the performance isn't that bad either.
I dunno, I could seriously see myself starting to use Windows full time and writing .NET programs in the near future. This technology (.NET, C#, VS Express) is really handy compared to what I'm used to.
Re: C# Tutorials
#8Operator overloading is super useful - I help maintain FluentCassandra and we overload the implicit conversion operators to make it seamless to convert from built-in .NET types and their associated Cassandra types. It makes a MASSIVE impact on the user experience and amount of boilerplate code it eliminates.
Doing ObjC for the past 5 years, I jumped on the Apple-fanatic bandwagon and hated loudly on operating overloading. But I really really loved being able to use + on two strings. So much nicer than `[a stringByAppendingString: b]`!
Re: C# Tutorials
#9Fortunately 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.
Re: C# Tutorials
#10In broad strokes, what are the differences between Java and C# and why should I bother with it? (Disclosure: I hate Java)
C# is years ahead on the language feature side:
- lambdas
- Expression trees
- sensible operator overloading
- value type semantics (you can define your own types that behave like primitives)
- reified generics instead of type erasure, which means that you can have an table (just two ints instead two pointers to Integer)
- "async monad" baked into the syntax
On the other hand, Java wins easily on the open source lib count