Hi All, I am a young professional that have recently begun to pick up C# so that I could add another programming language to my resume (I never learned Java either). The reason I haven't done this before is b/c I have always been content with what C++ and VB had provided. While I am sure this has been brought up before in this forum, I haven't yet seen a concrete explanation that I can relate to.
Now as I began exploring C# I came to the conclusion that it is unecessary given the availability of the other two. I have come to appreciate C++ for it's intense complexity when combining objects and pointers to create very dynamic programs, and VB on the opposite side, allowing one to quickly put together programs with simple scripting like language structure. C# seemed to fall in the middle, however I found that in most applications, I would rather use either C++ or VB since C# fell short when trying to achieve dynamic complexity that C++ offers, or it started to look too complicated and a C++ mimic when VB could do the job in a much more straightforward manner. I am not trying to bash C# but rather would like to see if someone can point out situations when one would choose C# rather than the other two (and the answer "cause that is the standard your employer uses" is not what I'm looking for). For example: 1. Pointers are much more straightforward syntacticly in C++ than in C# 2. Objects are more simplified in C# and therefore code is easy to come back to and read later (which is a good thing) but then again that just depends on your programming style in C++ 3. Quite complex programs can be designed in a matter of minutes in VB assuming you don't need to deal with complex object structures (for applications that require very basic input/output type structure). Even though VB can take care of objects to some degree too, at some point I'd rather revert to C++. Those are my preferences, and while it could boil down to just that, a mere personal preference, I don't see how C# can ever fit into a first pick. It could also be that I don't have enough experience with the language itself and am kind of turned off by the fact that I have not seen one book out there that mentions pointers or something similar (while collections seem to be the C# couterpart which I saw in some books, it does not seem to come close to the extensibility of pointers and VB has exactly the same thing available to it). Sorry for the long post, but your constructive input would really be appreciated. Thanks!
