Microsoft: Get rid of VB.NET -- now !

[Thomas C]

I think everyone is overlooking the core problem with multiple languages or
at least multiple language features. VB and C# are *the* Microsoft primary
..NET languages. It creates havoc when those languages do not support the
same feature set. Where it creates that havoc is in large development shops
where some people want to use VB and some want to use C#.

For example, right now, in .NET 1.x, I have recommended to all my clients
(I'm an independent developer) to use C#. Why? BecauseVB.NET's support for
operator and conversion overloads is ridiculously stupid. If they
standardize on one language, the language with the most supported framework
features, they will have the widest array of features available and they
will be able to interoperate easily.Coding everything to the CLS just isn't
an option. It is far too limiting.

VB.NET 2.0 improves this situation a great deal, but it still introduces
potential features that exist in one language and not the other. Further, it
really requires developments working in large groups to know both VB and C#.
Granted, I have already recommend that very thing just because public help
and commerical documenation can be in either language. While Microsoft
provided a great boost to book writing industry, it made it more difficult
on the development community.

I could live peacefully with both languages *if* it was possible to compile
a single solution with projects written in different .NET languages and
could step through code in either. That would make the situation far more
flexible and far more tolerable.


Thomas

 

[Ravichandran J.V.]

This is a recommendation to you, Spare Change.

Just refine your knowledge of English or look for some other search
engine or don't depend on others' solutions!

with regards,


J.V.Ravichandran
- http://www.geocities.com/
jvravichandran
- http://www.411asp.net/func/search?
qry=Ravichandran+J.V.&cob=aspnetpro
- http://www.southasianoutlook.com
- http://www.MSDNAA.Net
- http://www.csharphelp.com
- http://www.poetry.com/Publications/
display.asp?ID=P3966388&BN=999&PN=2
- Or, just search on "J.V.Ravichandran"
at http://www.Google.com

 

[Cor Ligthert]

Thomas,

Does this message of you mean that you want to get rid of C#?

I do not know if you ever saw Jon Skeet page (and he is absolute not a VBNet
person), however your message, accoording to Jon Skeets page, tells in my
opinion that Microsoft should stop with C#.

http://www.yoda.arachsys.com/csharp/faq/#vb.or.csharp

Before anyone would understand my message wrong, I am not for one program
language. That for the same reason why there are Alpha's and Beta's on the
world, that there are more natural languages on the world and that one
program language fits sometimes better a need than the other.

Cor

 

[clintonG]

Hello Cor,

I don't know how you assumed I said anything about VB developers
ability to write C#. My comments are about the 'perception' of VB
developers and RAD and how the perception that RAD can allow
software to be developed in as few as 3-4 lines of code as the RAD
proponents allude.

The marketplace is salivating for any opportunity to pay software
developers as low as possible and RAD gives employers and customers
every opportunity they need to lower wages on the basis of *their*
perception that RAD is some sort of magic wand.

--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET (e-mail address removed)
URL http://www.metromilwaukee.com/clintongallagher/

Clinton,

Why are you thinking that the ones who find VBNet in the current version
very productive, cannot write C# ?

You see still a lot of ancient programs be used (not including C# that),
however seldom you see stopping the evolution where the winner is the
strongest. (And in programming that is always the one which gives the
highest productivity at the lowest price, it is not a religion do you know)

Cor

"clintonG"

Well, even though you introduced some quibble (with which I
can agree) it seems the outcome will be the same and there will
be lots of VB developers trying to drink their regrets away when
the rest of us enlightened ones are busy getting paid the big bucks
because we adopted C# which will allow us to stay off the gallows
a bit longer than the other chumps

--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET (e-mail address removed)
URL http://www.metromilwaukee.com/clintongallagher/

wetdream...and

a addition
of

is

a

factor for, just look at java1.5(if you don't learn from the other side,
you
are pretty much doomed to failure after all), however it is a sign of
seperation. The differences will *not* be as pronounced as vb6 vs java,
for
example, for quite a while yet. These two languages started with

teh
same

trunk and are only now beginning to take full lives of their own.

It
may