Re: The Demise of C#
From: Kevin Spencer (kevin_at_DIESPAMMERSDIEtakempis.com)
Date: 02/23/05
- Next message: Ken Cox [Microsoft MVP]: "Re: The Demise of C#"
- Previous message: GMK: "Re: Displaying a aspx page within a page"
- In reply to: Karl Seguin: "Re: The Demise of C#"
- Next in thread: Scott Allen: "Re: The Demise of C#"
- Reply: Scott Allen: "Re: The Demise of C#"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Feb 2005 08:44:41 -0500
> This may be true today, but it's equally important to look at where the
> languages are going. It seems to me that in the 2.0 release, we are
> starting to see a divergence, albeit slight, between the two language
> which
> i expect will be a continuing trend. I agree that refactoring is only a
> tool which can easily be done as an addon, but that the C# IDE supports it
> and the VB.Net one doesn't suggests that the VB.Net team sees the needs of
> its developers as being different than those of C# developers. Other
> features such as My, Iterators and enhanced nullable types which are
> either
> in one language or another (anonymous functions in vb.net??) are all signs
> that MS is moving away from having the languages simply be "different
> syntax".
Very interesting point, Karl. Unfortunately, I think you may be right. I
only say unfortunately because I saw VB.Net as a chance to elevate existing
VB programmers to a deeper understanding of programming, which makes one a
better programmer overall. I have long resented the "dumbing down" of
programming that VB provided, allowing people to manipulate data that they
didn't have to understand. It sounds like Microsoft is backing away from
that bold move, and going back to the old "let the programmers be ignorant"
philosophy, which, IMHO, has resulted in a lot of poor programmers, and a
lot of poor programming.
> As far as the crappiness of VB programmers which was touched on by others,
> my personal opinion is that the programming language doesn't make the
> quality, it's the person behind the keyboard.
Absolutely. My point was that this is statistically more true today than
several years ago.
-- HTH, Kevin Spencer Microsoft MVP .Net Developer Neither a follower nor a lender be. "Karl Seguin" <karl REMOVE @ REMOVE openmymind REMOVEMETOO . ANDME net> wrote in message news:uRNRvVaGFHA.4004@tk2msftngp13.phx.gbl... > "Many C# developers today are basically VB.Net developers using a > different > syntax" > > This may be true today, but it's equally important to look at where the > languages are going. It seems to me that in the 2.0 release, we are > starting to see a divergence, albeit slight, between the two language > which > i expect will be a continuing trend. I agree that refactoring is only a > tool which can easily be done as an addon, but that the C# IDE supports it > and the VB.Net one doesn't suggests that the VB.Net team sees the needs of > its developers as being different than those of C# developers. Other > features such as My, Iterators and enhanced nullable types which are > either > in one language or another (anonymous functions in vb.net??) are all signs > that MS is moving away from having the languages simply be "different > syntax". > > As far as the crappiness of VB programmers which was touched on by others, > my personal opinion is that the programming language doesn't make the > quality, it's the person behind the keyboard. A bad programmer will > programming equally bad using whichever language. I think the belief that > there are simply more bad VB programmers out there is highly speculative > and > even if true, an HR departement would be foolish to ignore the fact that > there are plenty of good programmers in either language. Having said > that, > VB.Net does make it a little easier to be sloppy (option explicit and > strict, on error resume next, ....), but I'm sure that if someone wanted > to > they could come up, item for item, of a list of things C# allows which > could > be argued it shouldn't. > > Karl > -- > MY ASP.Net tutorials > http://www.openmymind.net/ > > > "Kevin Spencer" <kevin@DIESPAMMERSDIEtakempis.com> wrote in message > news:%23XnYteSGFHA.2876@TK2MSFTNGP12.phx.gbl... >> About 2 years ago, and as recently as perhaps 1 year ago, I can recall >> seeing many posts about what language to use with ASP.Net. The consensus > was >> that employers paid more for C# programmers, and it seems that C# became > the >> darling of the ASP.Net crowd. >> >> In the meantime, I have observed an interesting phenomenon. Originally, >> employers hired programmers who used C# because it was based on C, and >> the >> prevailing opinion was (and may still be) that C# developers were better >> because they must have known and/or practiced C or C++ at some time, >> which >> would make them better programmers overall. C and C++ are hard-core >> programming languages compared to VB. >> >> However, now that nearly everyone has jumped on the C# bandwagon, it >> seems >> to me that the distinction between the languages has nearly disappeared, > at >> least in terms of evaluating programmers for hire. There seem to be >> almost >> as many clueless C# developers out there as VB.Net developers. Many C# >> developers today are basically VB.Net developers using a different >> syntax. > I >> wonder if the employers have become aware of this trend? >> >> -- >> >> Kevin Spencer >> Microsoft MVP >> .Net Developer >> Neither a follower nor a lender be. >> >> > >
- Next message: Ken Cox [Microsoft MVP]: "Re: The Demise of C#"
- Previous message: GMK: "Re: Displaying a aspx page within a page"
- In reply to: Karl Seguin: "Re: The Demise of C#"
- Next in thread: Scott Allen: "Re: The Demise of C#"
- Reply: Scott Allen: "Re: The Demise of C#"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
