Re: The Demise of C#
From: IPGrunt (me_at_privacy.net)
Date: 02/25/05
- Next message: Michelle: "Re: Logg off users with session.timeout"
- Previous message: Michelle: "Re: datagrid question"
- In reply to: Karl Seguin: "Re: The Demise of C#"
- Next in thread: Geoff Willings: "RE: The Demise of C#"
- Messages sorted by: [ date ] [ thread ]
Date: 25 Feb 2005 15:30:01 GMT
On 23 Feb 2005, "Karl Seguin" <karl REMOVE @ REMOVE openmymind
REMOVEMETOO . ANDME net> postulated in 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
I wouldn't say the divergence between the languages is slight. For
instance, will VB.NET support generics?
C# is competing with Java for a major share of the Enterprise
development pie. The visionaries at M$ research thought it was worth
the rampup costs to introduce a new language to get the state-of-the-
art features needed to take the sdk to a new level of security and
interoperability. In other words, dot net needed C# and C# needed dot
net.
I'm not sure what Visual Basic.net is moving towards, but the
development of VB.Net serves a couple of strategic purposes for M$.
First, it satisfies the many legacy developers out there that have
built an entire industry around VB coders and VB applications. VB.NET
gives the VB contingent new legs to carry them for years down the
line.
VB.NET also provides case-study data on creating dot net languages.
It gives credibility to the point that dot net is not C#-centric, as
the Win32 is C++ centric, and in this way demonstrates to the
language community the flexibility and viability of the dot net
platform as a target machine.
JMHO.
-- ipgrunt
- Next message: Michelle: "Re: Logg off users with session.timeout"
- Previous message: Michelle: "Re: datagrid question"
- In reply to: Karl Seguin: "Re: The Demise of C#"
- Next in thread: Geoff Willings: "RE: The Demise of C#"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
