Just a note, not a war.

Scoble says that VB.NET is not dead, and it's actually picking up some steam inside MS. *whew*. To anyone that said that my career was dead if I didn't switch to C#: "I fart in your general direction. Your mother was a hamster, and your father smelt of elderberries." Hey Scott, name that movie.

6 Comments

  • Why not do both? It isn't hard. Personally, I prefer C# due to what I perceive as its "first class" status. But I see a place for VB, and other languages.

  • I can code both, but my primary language is VB.NET.

  • Looks like C# still pays more...according to the recent Fawcette survey! I was an old VB coder - and VBScript in the ASP times. When I started learning .NET, I began by using VB.NET...hmm..I did not enjoy it, it has all the clumsiness of VB (CType...ick!), so I decided to go for C# instead. C# has the advantage that it's strict by default (no Option Strict or Option Explicit), is so similar to Java as to be a very simple transition - java coders are in general better OO coders than VB ones - sorry, they just are! I could also more easily repurpose my J2EE architecture skills into C# - I have no clue why it was easier, just seemed more natural.


    Also, the jobs market here is FAR better for C# (added advantage, you can flip back to Java more easily if need be - the job market is really tricky!)

  • I should clarify my position a bit. Does it really matter? But, yeah, if you want status at Microsoft, it seems most of the hard-core folks I know here at Microsoft are C# types.

  • I think that goes in line with Scott's comment that C3-ers are usually better at OOP cause they come from Java. I think if VBers actually <i>understood</i> OOP, which is what I am focusing on, then maybe they would get somewhere, especially at MS.

  • No one named the movie. It was Monty Python and the Holy Grail.

Comments have been disabled for this content.