Comments on: Learning C#: Early Impressions http://darylteo.com/blog/2008/12/21/learning-c-early-impressions/ Bits and blobs on anything tech Sat, 31 Dec 2011 19:51:45 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Aaron http://darylteo.com/blog/2008/12/21/learning-c-early-impressions/comment-page-1/#comment-9042 Aaron Mon, 12 Jan 2009 13:04:42 +0000 http://darylteo.com/blog/?p=194#comment-9042 Java's protected and default visibility are retarded. C++ and C# make more sense(not that I develop in either of those anyway), Java’s protected and default visibility are retarded.

C++ and C# make more sense(not that I develop in either of those anyway),

]]> By: Daryl http://darylteo.com/blog/2008/12/21/learning-c-early-impressions/comment-page-1/#comment-8976 Daryl Sun, 04 Jan 2009 13:24:09 +0000 http://darylteo.com/blog/?p=194#comment-8976 Welcome Sam to my humble home. I am glad to see your comment :) I suppose alot of these things are a matter of adjusting to the language and its "features" (something I reiterate alot in the post, as you might have noticed). As for the IDE... I could have a field day with that one! (Why doesn't Eclipse have a .NET plugin!?!) Perhaps I will write about it when I finally use Visual Studio 2008, since it would be more relevant. From what I heard, not much has changed either. Again, thank you for your comment and I hope to see you around more :) Nice site btw. Cheers Daryl Welcome Sam to my humble home. I am glad to see your comment :)

I suppose alot of these things are a matter of adjusting to the language and its “features” (something I reiterate alot in the post, as you might have noticed).

As for the IDE… I could have a field day with that one! (Why doesn’t Eclipse have a .NET plugin!?!) Perhaps I will write about it when I finally use Visual Studio 2008, since it would be more relevant. From what I heard, not much has changed either.

Again, thank you for your comment and I hope to see you around more :) Nice site btw.

Cheers
Daryl

]]> By: Sam http://darylteo.com/blog/2008/12/21/learning-c-early-impressions/comment-page-1/#comment-8975 Sam Sun, 04 Jan 2009 12:16:38 +0000 http://darylteo.com/blog/?p=194#comment-8975 I'm doing this from the other way around - learning Java after having a solid background in C#. I'd say its a more difficult that way, because C# gives you all kinds of nice constructs in the language, like delegates, event handlers, LINQ, lambda expressions, to make things easier (possibly at the expense of readability if you're not used to it), which Java doesn't have. About properties - I really missed these. If the lack of the 'set' keyword is confusing, declaring and setting variables must be confusing too :) As for knowing if something is read-only - I assume you're using an IDE, in which case it will tell you if something is read-only by the icon and the popup hint. It takes time to get used to I suppose. The problem with properties is that it implies that it is just as simple as setting/getting a variable, when the get/set code might in fact be doing lengthy calculations, or has side-effects, neither which is conveyed in the syntax. Then again, that's really abusing properties, and can be done in Java too. About subclasses - all .NET interfaces start with an I, e.g. ISerializable. This is by convention but is fairly strongly adhered to (and might even produce a warning in the IDE). I do like the Java syntax here though. And operator overloading - haven't had the need to use it myself, but what about for matrix classes, or timespans? There's a logical reason there. Someone would have to have a pretty good reason to operator overload though, and it should only replace functionality for specific cases (e.g. between two matrices, not anything else). Looking forward to hearing the rant on ASP.NET :) I’m doing this from the other way around – learning Java after having a solid background in C#. I’d say its a more difficult that way, because C# gives you all kinds of nice constructs in the language, like delegates, event handlers, LINQ, lambda expressions, to make things easier (possibly at the expense of readability if you’re not used to it), which Java doesn’t have.

About properties – I really missed these. If the lack of the ‘set’ keyword is confusing, declaring and setting variables must be confusing too :)

As for knowing if something is read-only – I assume you’re using an IDE, in which case it will tell you if something is read-only by the icon and the popup hint. It takes time to get used to I suppose.

The problem with properties is that it implies that it is just as simple as setting/getting a variable, when the get/set code might in fact be doing lengthy calculations, or has side-effects, neither which is conveyed in the syntax. Then again, that’s really abusing properties, and can be done in Java too.

About subclasses – all .NET interfaces start with an I, e.g. ISerializable. This is by convention but is fairly strongly adhered to (and might even produce a warning in the IDE). I do like the Java syntax here though.

And operator overloading – haven’t had the need to use it myself, but what about for matrix classes, or timespans? There’s a logical reason there. Someone would have to have a pretty good reason to operator overload though, and it should only replace functionality for specific cases (e.g. between two matrices, not anything else).

Looking forward to hearing the rant on ASP.NET :)

]]>