A well-deserved smack back to some C# zealotry

Someone sent me a link to this page, which lists seven reasons why VB.NET programmers should be converted into C# programmers, and I just had to respond. It's crap like this that does nothing but obfuscate the real issues. Let me respond to each “reason“

> #1) Developers who program primarily in C# earn 26 percent more than those who develop primarily in Visual Basic .NET. (Source: 2003 Salary Survey: How Do Your Earnings Stack Up?, Visual Studio Magazine, June 2003) >

I don't doubt it. Most C# programmers are former C++ programmers who typically have more CS education and low-level understanding of computers. There are (or were, I should say) more VB programmers out there than programmers of any other language. Anyone who understands macroeconomics knows that when there are 10 VB programmers for every available VB position, and 2 C++ programmers for every C++ position, the C++ programmer is going to make more money. Those VB programmers that learn VB.NET and keep their jobs don't immediately get a raise to match the C++ developer's salary. The C++ developer who learns C# does not take a pay cut.

> 2) C# just looks more elegant because it was consistently designed. VB.Net was evolved over many years and has inconsistencies. <

This is completely a matter of personal preference and is NOT a reason to switch languages. In fact, I think C# looks ugly. To me, it's not as readable. So, I can make the same argument for VB.NET. Matters of personal preference are not arguments for switching. As for being elegant, I'll match the elegance of my code to yours any day, no matter what language you wrote it in.

> 3) C# is closer to Java which means it is easier for you to move to or from Java. This is good for your career. <

So, now “because you can convert to Java“ is a reason for converting to C# ?  Planning on converting to Java anytime soon?

> 4) C# is perceived as a “real” language where VB.Net is still perceived as a “toy” language. <

I've said it before, and I'll say it again. It's because of stupid statements like this that we have this perception. Let's ask Dan Appleman's customers. Dan is a dual CS/EE major and spent many years writing components in C++. His company, Desaware, recently published a suite of all their .NET components and tools WITH SOURCE. The language they were all written in? VB.NET.  Are you saying that Dan Appleman uses a toy language to make toy components that companies like NASA use for their toy software to land toy rovers on Mars?  Give me a fucking break.

> 5) Microsoft does all of its internal .Net development in C#. Even MS thinks C# is the better language. <

Microsoft is made up almost completely of C++ programmers. Naturally, they are going to latch on to C# as their development language. Naturally the C# programmers at MS are going to think C# is better than VB.NET. However, the VB.NET team and a large (and still growing) population of C#/VB.NET developers at Microsoft spend every waking moment thinking of how to improve VB.NET as a language and a development environment.

I know some assembler programmers that make the best FFT matrix computational components. I use them in VB.NET. But Carl, these guys obviously think Assembler is the best language!

> 6) C# has the following features which VB.Net doesn’t have: (Operator overloading, XML code documentation, Ability to write “unsafe” code for better interoperability) <


VB.NET Whidbey has Operator overloading and XML Code Documentation. As for unsafe code, this has never been a problem for the VB.NET developers I know. And, if it is a problem, I can write a small DLL in C# and call it from VB.NET. That's like buying a new car because the cigarette lighter broke. Just fix the freaking lighter.

If anyone should be making the feature comparison argument, it is the VB.NET programmers. VB.NET has a background compiler, which compiles a statement immediately after writing it. This makes intellisense and design-time error reporting work. While your brain is busy decoding cryptic error messages, mine is moving on to a critical piece of business logic.

> 7) Microsoft is actively adding new useful features to C# including generics, iterators, anonymous methods, and partial types.<

VB.NET 2005 has generics and partial types, so this argument is lame. I often hear the rebuttal, “VB.NET developers aren't savvy enough to use features like generics anyway“ which is nothing but pompous fascist bullshit.

When are these C# zealots going to stop telling us VB.NET programmers that we suck, our language sucks, and that we don't know how to use our own language. I'm not talking about the civilized C# programmers, such as those at Microsoft, and the leaders in the .NET community. I'm talking about zealots who propagate yesterday's myths as reasons for their superiority.

Just use C# and shut up.


  • There is no good reason in modern computing for language case sensitivity. C types make excuses galore for why case sensitivity is a good thing but we all know it's a pile of poop. The machine is supposed to do the work, not the human! Just admit that Kernighan and Ritchie got it wrong and let's be done with case sensitivity already cause it really, really sucks.


  • Ahem,

    Ah, Carl, if you feel that strongly, perhaps you should take out a contract on this guy… ;)

    As for me, (and I’ve been programming for a couple three decades too), I prefer Visual Basic as it’s more productive. I’ve been a development manager as well and as such, I prefer languages that my staff can use more efficiently. Managers and the developers they hire are rewarded by the number of problems they solve in a period of time. To me C# has been a “readable” language, but far harder to work with because it has not been as well integrated with the Visual Studio .NET IDE. In Visual Basic when I make a change to a variable or change its scope, I don’t have to do anything—the Visual Basic IDE takes care of the details—I have never had to. Visual Basic’s just easier to use for any number of reasons. The fact that there are billions of lines of Visual Basic code out there to draw on is another appealing factor. Sure, some of it’s going to have to be recoded to go use the Framework. We do this every few years to clean out the closet.

    Sure, if you come from Java or C++, you’re going to want to write to C#. That’s fine. Statistically, those people do make more—but I can prove conclusively any fact you care to name given the ability to pick the sample. For example, I can prove that Visual Basic developers make more money simply by adding up the salaries of every man, woman and child that programs in Visual Basic—and include the professional developers along with the “paradevelopers” like the physicians, pundits, prosecutors, plumbers (who make even more) and politicians who make programming Visual Basic part of their job. Hell, the politicians alone would throw the income curve way off. Does that make Visual Basic more important or C# less important? Nah. It just means each has chosen the right language for the person with the problem.

    Visual Basic is about productivity—doing more with fewer mistakes by more people without the need for specialized training. The Framework is about that too. The fact that you can use Visual Basic, or C# or any of a couple dozen other languages is immaterial. Saying one language is “better” than another is like saying Aramaic or Greek is better than English because that’s what the bible was written in and you can’t understand Christianity without reading and knowing these ancient tongues.

    Carl’s right. Developers should not choose a language for any of the reasons he mentions. They should choose a language with which they are most comfortable and can make the most productive contribution to their company and to themselves.

    Bill Vaughn

  • I think there are two issues at work here.

    I absolutely think that a project team must choose a language and stick with it for all code they create. Note I said create, not consume. Proliferation of multiple languages within a project is the road to madness.

    That being said I think the strongest argument for that language choice is what are the developers backgrounds. If C/C++ developers great use C#. If Visual Basic/VBScript developers then use VB.NET. They aren't so different that the odd team member who doesn't sync up with the rest of the teams background can't catch on.

    Now this is complicated by the foolish resolve of each of the language teams to further differentiate the languages so they can &quot;compete&quot; against one another. I think this is just going to promote more of the us vs. them mentality that is already swirling around language choice.

  • Carl, the elegancetech page is silly, but you're not doing much better.

    POINT 2: While I'd agree that it's mostly a personal preference issue, VB really does have some cruft. It's a minor but valid point.

    POINT 4: You can rail against the injustice as much as you want, but like it or not, their statement is true. It's not fair, but many C++ people view VB as a toy language.

    Blaming the situation on people who report it is unreasonable.

    The real cause is that C++ acts as a gatekeeper. It's such a pain to learn that only the dedicated use it much. On the other hand, VB has always been easy, so even a clueless hobbyist can release buggy shareware.

    POINT 6: You are talking about a future version, not what's currently being sold.

    Anyway, I used VB from version 1 to version 6. It was wonderful for utilities and small apps, but I found it extremely constricting at times. I preferred C++ for professional projects.

    Now with .Net, VB is a more full-featured language, but it still doesn't have unmanaged code. (Yes, I need unmanaged code.)

    Luckily, C# has most of the development speed and ease-of-use of VB combined with most of the power and respect of C++.

  • My.Programming.Language.Is.Better.Than.Yours()


  • First of all, I will admit that I am actually a C# guy myself and love it. However, I totally agree with Carl that the reasons are total bull-honkey. With that said, I believe that choosing which language you use is mostly just a personal decision (it's all basically syntactical sugar anyways (since it all gets compiled down to MSIL (disregarding Unmanaged code of course))).

    Even though I personally like C#, I work with both C# and VB.NET and there are specific things that I like about both languages. With VB.NET, there are two primary reasons that I love working with it when I do: background compliation, and the AddressOf operator (which is an *awesome* tool to have when working with delegates). I can't explain really why I prefer C#, I think it is as simple as me liking curly braces instead of &quot;End If&quot; kinds of things.

    However, it is a pet peeve of mine when someone tries to say that C# is superior to VB.NET. This is totally bogus and it just tells me how un-informed the person actually is. After all, if you get rid of the level of abstraction, we are all just coding in MSIL to begin with (assuming all the codebase is managed). Both languages have their strengths and their weaknesses. I wish people could just deal with that and accept that fact. &quot;I have a dream, where all languages are created equal&quot;, yada yada yada.

    Nice post Carl! :)

  • Carl, you said: &quot;Their statement is false. The statement 'VB.NET is a toy language' Is false. The only way to say it truthfully is 'There is a perception that VB.NET is a toy language.'&quot;

    But yheir website says: &quot;C# is perceived as a 'real' language where VB.Net is still perceived as a 'toy' language.&quot;

    They are stating the unpleasant truth, and it's exactly what you say they should say. Maybe they changed their website after you wrote your post?

  • No, I was just ranting. You're right of course. It still makes me mad that I rarely hear people saying &quot;VB is a toy language&quot; anymore. All I hear is that people percieve of it. Fair enough. Let's stop talking about the minority who keey saying the sky is falling, and shine a light on reality. Nuff said.

  • You guys missed the best one:

    2. &quot;Your developers will be more productive because they will work in a language that they like.&quot;

    What, because C# is the FUN language? Parties with curly braces?

  • WHo woULD neED CASE SensITIVIty tHESe DAYs QuestIOn MARK anD WHY woULD aNyOnE uSE PUNctaTION whEN YOu can spELL iT OUt QUEstIon mARk THoSE are clEARly DRAGginG PRODUCTIVITY DowN CoMMa MAkiNG thE cOdE difFICult tO reAD Dot

  • Find me a consulting shop that says they will charge you more if you insist on having it written in VB.NET. If all the stuff we argue about doesn't manifest itself in something measurable, then by definition, it doesn't matter.

  • While I am a csharper, I completely agree with you Carl. It's time for everyone to move on from these types for arguments. The types of people that continue to use these arguments are so rooted in the past they've failed to realize that its all about the Framework today, not the language. The analogy I commonly use is this: Say you need to write a letter to someone. You have a pen, a pencil and a piece of paper. C# is the pen and VB.NET is the pencil (or the otherway around), and the letter is the IL code. It doesn't matter which one you write it with, the letter's content is the same.

  • &quot;Um. VB.NET Whidbey has operator overloading AND XML Document generation. Look it up. &quot;

    Where can I buy VB.NET Whidbey? Version VS.NET 2008 also has great new features. And no-one can use them today.

    Perhaps YOU should look up something, like the meaning of the words &quot;Not yet available&quot;.

    Today, tomorrow and even the first half of 2005 I can't use what you say that's available :)

    &quot;It's still not enough to make me switch.&quot;

    That wasn't my intention, everybody should use what he/she thinks is best for his/her software development. That also means that if C# is better for some sort of software development, people shouldn't whine but switch, the same goes for the other way around of course. Like the constant stream of whining about E&amp;C in C# or the lack thereof. If people like it so much, use the tool that has it. :)

  • I think one C#/VB.NET difference is even more simple than that.

    Its a name thing. Sharp vs Basic

    Now imagine you are non techy employer deciding who to hire or what wage to pay, you know nothing of curly brackets or overloads, do you pay more to the &quot;Sharp Programmer&quot; or to the &quot;Basic Programmer&quot; ?

    Next your a software house selling a custom solution to your &quot;hasn't a clue&quot; customer, Do you say &quot;We have a team of Sharp Programmers or a team of Basic Programmers ?&quot;

    OK, so all the VB houses will say &quot;We have a team of .Net Programmers&quot; but they are still bidding against the company down the road that has a &quot;Team of Sharp .Net Programmers&quot;

    I think it is a marketing thing, perhaps it will change as business discovers it can get 5 vb programmers for the price of 4 c# programmers, but first it has to overcome the word BASIC, im not sure that will ever happen.

  • Search for truth, it will be found.

    I like not worrying about case, but still use case for my own pleasure. (VB.Net allows me to choose.)

    It's also a matter of syntax. Csharpers sometimes come across with the attitude 'If you're not doing it the hard way, you're not a real programmer.' Maybe they don't say it outright, but it comes across...

    Would you like to drive a car with an engine you build yourself, simply because a real driver builds his car from scratch? Silly really. If we want to do things the hard way, let's say a kit car, fine... it's a good thing to know how to do. But if your out their trying to get a solid product in short time, your not going to go and use something that restricts your speed.

    Use the right tool for the job. If you can do the job faster in VB, do it. If C# is better for the job at hand, use that. If you have a team and can have some people that dabble in both, better yet.

    Me, I'm VB. I came from the ranks of hobbyist, but would not consider myself hobbyist now. I stick with VB cause it does a professional job, but doesn't take me a lot of time.

  • It's about the money. If the C# community can get the perception that thiers is the 'Real Language' and has less resources, then they will be able to charge the client more for the work. Time to get some real world studies to see if 2 similiarly skilled developers can develop the same code in different languages and see who is the most productive.

    I also teach VB.net and C#.net, and the studens seeing C# for the first time are intimidated by the syntax structure, where similiar students in thge VB.net courses bet teh syntax structure immediately. It is easier for them to read, and see errors. (I spend more time in the C# class checking for ;'s and that is just plain dumb)


  • Tom: well in VB.NET you have to check for '_' at the end of a wrapped line :) A C# developer hardly forgets a ';' like a VB.NET developer hardly forgets the '_', both because of the editor. If you develop C# or VB.NET in notepad for example, it would be much harder (and as I've done excessive C# to VB.NET porting in templates (thus no intellisense) I can tell you writing VB.NET without the VB.NET editor is no picknick ;))

  • I have used VB since VBDOS and currently use C# 70% of the time though I like the appearance of well coded Visual Basic.Net better…

    &gt;&quot;VB.NET is a toy language&quot;

    I can pull up Visual Studio.Net – File &gt; New &gt; C# ASP.Net web application. I can drag a button on to the form. Double click the button and add 1000 lines of interface, business and data access logic directly into the Button1_Click event. I can do this in VB too without semicolons… In reality either language (as most languages) can be used ineffectively.

    - I find often less technical individuals (customers) find it much easier to read and follow VisualBasic.Net code. It can be an advantage to explain simple logic sitting next to a user viewing clear written English on the screen. In a similar discussion using C# you would really have to go to diagram because it is much less readable to “the average person”. I personally know of developers who do realize that because C# code is not as easily read initially by an “untamed eye” due to additional syntactical elements and arrangements it is perceived as more complicated and also therefore perceived as “the more powerful language” and this is why they use it...

    I develop mostly in C# because of the uneducated developers and companies you speak of that assume C# is better... Unfortunately when opportunities present themselves its easier to implement with C# then to evangelize why I should be compensated the same with VB.NET after showing them err of their misguided ways...

    &gt;“Saying one language is “better” than another is like saying Aramaic or Greek is better than English because that’s what the bible was written in and you can’t understand Christianity without reading and knowing these ancient tongues.”

    Knowing Aramaic and/or Greek can be helpful in knowing actual words used and their original meanings prior to English and other translations such as Petros etc… We do have references for such not requiring us to memorize the entire language though….

  • A famous person once said, &quot;Don't Mistake Kindness for Weakness.&quot; I would like to COOP that statement to, &quot;Don't mistake Ease of Use for Lack of Power&quot;. Many people underestimate the power of simplicity, I remember a government employee telling me that MS-Word wasn't a real Word processor, Word Perfect would prevail in the end. Where is Word Perfect today? (Remember reveal codes?) When i first saw Word, I was hooked, when I first used VB.NET I was hooked. C# has too many syntactical anomolies for me to use easily. It's not that I am too stupid to understand it, it's just that I DON'T CARE or HAVE THE TIME to learn all of the syntax and place in my mental framework. Nice one Carl, it's time the gloves came off!

  • I'm surprised they didn't tout the &quot;C# programmers are paid more&quot; argument in the &quot;For The Manager&quot; section! Oh well, we all know managers are too dumb to look in that other column.

    I actually really enjoyed the User Testimonials: &quot;Great tool to develop the application in VB.Net as your preferred language but then deploy and expose the code as C#&quot;. Gee, and I thought you deployed assemblies, not source code. Back to the docs for me!

  • Well, despite being quoted here, I already weighed in on this topic in my ebook &quot;Visual Basic .NET or C#: Which to Choose&quot;. There I go into a great deal of depth comparing the two languages and suggesting when you might want to choose one over the other. Right now it's really a wash - both languages have strengths and weaknesses.

    I happen to personally prefer VB .NET because I really like background compilation - it makes me more productive. The lack of unsafe code doesn't bother me, because in applications where I really need unsafe code I'm doing a lot of mixing of COM/pointers and .NET, and for those I like to use C++ - which is really brilliant at mixing safe/unsafe/managed/unmanaged.

    I'll be reviewing VB .NET and C# again, probably with the next Whidbey Beta. Based on what I've seen so far, I don't expect either to prove decisively better than the other.

    The truth is, as any real .NET developer knows - it's not about the language, it's about the framework. Any C# developer worth his while can read and write VB .NET and vice versa.


  • Oh, and by the way... I did like Carl's response very much. Sometimes extremist zeolots need to be responded to with extremist zeolotry.

    I took a slightly different swing at it in my recent VS Magazing article.


  • As a response to an earlier comment - XML documentation is in fact available right now. You can download the VB Powertoys from GotDotNet.com, and/or use it with nDoc. With Whidbey, the feature doesn't require a separate download.

    &gt; Now with .Net, VB is a more full-featured language, but it still doesn't have unmanaged code. (Yes, I need unmanaged code.) &lt;

    Well, I guess that means you can't use C# either. The only language MS makes that targets the .NET platform AND compiles *unmanaged* code is MC++. I really am tired of repeating this.

  • That's true. Unsafe code is not Unmanaged code. C# is managed, even when using pointers.

  • I'm surprised that no one pointed out that the source of all this debate is a site whose business is specifically in converting VB code to C#. Why would anyone expect an objective viewpoint from them?

  • I think the point is entirely missed here. Having programmed in many languages (FORTRAN, Pascal, C++, Java, etc) Ive learned one thing; great programming transcends language. I could give Lance Armstrong the cheapest bike in the world, and hed still kick my ass on the most expensive bike in the world. Its not the language, its the expression of the idea. These so called zealots of any language will always be just mediocre programmers until they learn to get pass language obsession. By the way I dont program in VB or C#, I program .Net.

  • mike,

    &quot;I'm surprised that no one pointed out that the source of all this debate is a site whose business is specifically in converting VB code to C#.&quot;

    That's kind of what I was getting at by poking fun at the &quot;User Testimonials&quot; and &quot;For The Manager&quot; sections of their site. What we've got here is clumsy marketing-speak, not true zealotry.

  • Well, its an old argument...

    I want to weigh in and point out that they are different languages. It does matter which you work with. There are things better and worse in each, and each language team is focused on fixing different things. Frans is right that there's some oversights in interfaces in VB (I think Whidbey may address this one). But have you really tried to manage various scoping options in interface implementations in C# - its a piece of cake in VB. You can't shadow by name in C# at all. VB's declarative, C# isn't (except attributes). VB's like a partner, C#'s like a tool. Some people like tool's and C# works like a computer - which can be good if you like that. My sons prefer C#, I prefer VB.

    My point is not that VB is better, but that its not just an unimportant casual preference, like for different types of chocolate. It's a match between the way you think and the way the language works. If I was a manager, I'd give this test to my developers. I could not afford the logic errors that would result if they're immediate (2 second) reaction was wrong. (You can translate to VB.NET)

    int i = 2;

    int j = 3;

    if (i/j &gt; 0) then

    { /* Is this code executed? */ }

    Also, the salary survey that the website quoted was fatally flawed. It was from a time that far more C# programmers were consultants and far more VB.NET programmers were hires. The survey did not account for this, and comparing cash income from conslutants and hires is just stupid.

  • This debate is soooooo tired. Like Dan said, it's ALL about the framework.

  • What a thread this created!

    I use C#, but I won't count myself an elitist -- I think that the whole .Net family is incredible technology.

    For me, there is one interesting theme that plays through these C# vs VB arguments: There _are_ differences in the languages. We know that .net languages are allowed to be different, as long as they are compliant with some base rules.

    For me, here's the million dollar question: Why do VB.Net and C# differ in the ways that they do? What's the message? What's the theme? Is there coordination between the C# and VB.net teams, where they decide what sensible differentiation to apply, or are the differences that we see just the result of open competition or at least a lack of coordination between the VB and C# teams?

    There just doesn't seem to be a consitent plan dividing the features. And for that matter, should there be features absent from either language? If VB and C# are both built on .Net, and they both leverage the same framework, and are built by the same company, and they are both billed as industrial-strength languages, why shouldn't VB have every feature that is in C# and vice-versa?

  • These guys are selling their little program to convert from VB .NET to C#. So it makes sense for them to make up stupid reasons to convert VB .NET to C# to sell their crap.

  • Rob Teixeira, I couldn't find the XML documenter.

  • I guess am chiming in a bit late, but I still want to make a point.

    It seems like I have heard a similar argument before, I wonder where…. Ahhh yes, I have this very same argument all the time with “real” CS geeks, who think that using a “toolkit” like the .NET framework is for sissies. They can write wrapper classes better! They can make better parsers in their sleep! They can, well you get the point. While I don’t doubt that certain talented people can write a better framework than the folks at MS. Who cares! I need productivity, I don’t have the time to write it myself, so I’ll use what ever tool fits the job at hand! The square peg in round whole example Carl uses all the time! So it seems we should band together under the Framework and not which language. After all there are lots of CS depts. in colleges all over the country that still only teach C, C++ and Java, and , .NET is viewed as part of the Evil empires goal to take over the world. And so in closing, while the latter statement might be true (jk), let’s convince the low level folks that writing your own shell and parsers is not the way the real world moves, unless of course you’re working on a framework team ;).

    My $5 worth!

  • Three cheers for the &quot;SLECT CASE&quot; statement in Vb.net. This statement is flexible, elegant and powerful. C#'s is clumsy, constricted and downright ugly.

    In my opinion, of course!

    All you zealots, GET A LIFE!!!


  • Carl,

    You also forgot to add that VB coders bathe and wash their hair more! Cleanliness is next to Gatesliness you know.

  • Well, it's really the C++ programmers that have dirty hair. :)

  • Yeah well &quot;those people&quot; all look the same to me anyways.

  • Don't you guys have anything better to do with your time?

    Grow up.

  • Carl,

    It's not that C# is a better programming language than VB (even thought it really is). You are correct it is a personal preference. It's just that people who prefer C# are better.

    anywho, I take it you are a VB Man. I was a VBer until I figured out c# is less typing. To me that is the major advantage. Less Verbosity.

  • My personal preference is C#. I don't believe VB.NET should have come to exist at all, but I have begun to acknowledge its place for the thousands of VB developers out there. It is though, just syntactic sugar for those people, with only a skin-deep resemblence to VB6.

    Point 2 - I would agree with. C# doesnt try to turn code into babytalk, rather allow developers to pick it up quickly because of it's remarkable similarity to Java, and it's syntactic similarity to C/C++, PHP, Java, JavaScript etc.

    Point 3 - Is of course right.

    Point 4 - Well, the reasoning for such comments should also be obvious, but I am a strong proponent of the 'Why make it more difficult than needs be' argument. I would have given this same argument more credit for VB6 because it was it's own language with it's own origins.

    Point 5 - Wouldn't surprise me. But I am not in that team so what would I know?

    Point 6 - Now come on.. Wrong? Because it's GOING to be in the next version? Would it be wrong to say VB.NET 2002 developers didn't have access to bitshift operators until 2003 came out?

    Anyway, really I don't mind what people use until it affects my work directly, in which case I will of course TRY to steer clear of VB.NET

  • Point #7 is the real interesting one. The [microsoft] developers for Whidbey placed generics as #17 on their priority list. It was #1 on the list for the C# developers.

    As (beta) shipment neared, it was apparant that they were NOT going to get to item #17. An uproar [internal to MS] occured, &quot;We have to have generics BECAUSE C# does!&quot;.

    As a result 6 items which were deemed more important than generics [by user survey, internal analysis, etc] were abandoned for this release!!!!

    Now we hav a language wich supports a given feature, NOT because it was a top ranking request, NOT because it was internally deemed technically important, BUT simply to appease a complaint that was marketing related!

  • What are the main arguments for/against case-sensitivity in C#? I like being able to use TitleCase for my methods and properties, and thisCase for my parameters and fields. (I hate using under_stupid_scores for things.

  • I only WISH I had all of your problems. I came from a .NET shop and preferred VB.NET, although I didn't mind C# because it was similiar to Java. I always liked Java, but thought that its biggest problem was the lack of a good IDE. Then along came .NET and C# which made that mostly moot since C# is so Java-eque.

    My problem now is I transferred to a place where they are using LOTUS-FREAKING-NOTES as the application development "language". The worst part is that I can't even find any good resource arguments online to back up my claims that Lotus Notes is garbage and that we should switch to a real programming language like Java or .NET because it's like trying to make an argument in favor of using a car vs. a tricycle. The comparison is so absurd its not even necessary.

    I'm still banging my head on the desk from frustration. Using Lotus Notes as an application development language is about as effective and fun as trying to build a house using a pile of toothpicks and a screwdriver. Use C# or VB.NET and count your blessings :(

  • I think VB.Net and C++.Net are a Complete Couple and C# is Something Suspended Between Them

  • with csharp, vb,cplusplus do

    translation: all of the above comments tell me you should all be using delphi anyway.

  • oh baby the best is vb.net ........
    C# codes are hard and uncomfortable
    but vb codes are as powerful as c# codes but more easier

  • This approach makes some fairly unconsidered assumptions. ,

  • Yes there should realize the reader to RSS my feed to RSS commentary, quite simply

  • celZCk A round of applause for your post.Much thanks again. Cool.

  • That is the suitable blog for anyone who desires to search out out about this topic. You realize so much its virtually arduous to argue with you (not that I truly would want…HaHa). You positively put a new spin on a subject thats been written about for years. Nice stuff, just nice!

  • 1QGV1c Very neat blog.Thanks Again. Much obliged.

Comments have been disabled for this content.