Unifying Language.Net

[koorb]

Is there any reason why Microsoft is keeping the languages separate or
will they eventual replace all the languages with one, just to
simplify?

And why do people keep talking about switching to C#.Net, is there
something special planned for it?

 

[Bob Lehmann]

How would unifying the languages simplify things? Simplify for whom?

What do you mean "people keep talking about switching to C#.Net"? People are
also talking about switching to VB.Net & J#.

Bob Lehmann

 

[Herfried K. Wagner [MVP]]

Is there any reason why Microsoft is keeping the languages separate or
will they eventual replace all the languages with one, just to
simplify?

Mhm. That's the main reason why .NET exists. Multiple
languages/compilers written by different companies share the same
execution environment and class framework. The number of programming
languages for .NET will grow. BTW, I don't see how one language would
simplify things.

And why do people keep talking about switching to C#.Net, is there
something special planned for it?

What people are talking about that? Switching from what to C#? Java?
VB6? Don't take such discussions serious.

 

[koorb]

How would unifying the languages simplify things? Simplify for whom?

Industries are built on standards. Since .Net unifies the languages
with a big leash, I just wondered if there where any plans to finish
the job.

What do you mean "people keep talking about switching to C#.Net"? People are
also talking about switching to VB.Net & J#.

Bob Lehmann

I have been doing searches through Usenet and the most common .Net
language vs thread, is VB Vs C#. VB because of it's beginner friendly
approach and then nobody mentions why C#, but a lot of people keep
brining it up.
For example
http://tinyurl.com/4593f

 

[David]

Is there any reason why Microsoft is keeping the languages separate or
will they eventual replace all the languages with one, just to
simplify?

In all probability, both VB.Net and C# are here to stay ("stay" in
computer terms, anyway), both have large user bases. J# and c++/managed
are only a little less secure, though if java ever tanks, J# will be
dropped in a second IMO.

But I'd expect a whole lot of the other language implementations to go
away, especially the small ones that MS did for the original framework
largely so that marketing could boast of .NET's multi-language
capabilities.

And why do people keep talking about switching to C#.Net, is there
something special planned for it?

That depends on who you hear talking. In most US markets, C#
programmers make more money on average than VB.Net programmers, so
there's always some talk on those grounds. And it seems that every time
that Whidbey news comes out, there's some grumbling about VB.Net
programmers being treated as second-class programmers, but I don't
anticipate many people switching because of it.

 

[Lucas Tam]

Is there any reason why Microsoft is keeping the languages separate or
will they eventual replace all the languages with one, just to
simplify?

No - Multiple languages is one of .NET's major features.

And why do people keep talking about switching to C#.Net, is there
something special planned for it?

Only because C# is new... and the syntax is comfortable for those who use C
or Java.

Well... C# does have a couple of features not found in VB.NET, but they're
relatively minor (i.e. the XML Help documentor).

 

[Jeff Johnson]

Only because C# is new... and the syntax is comfortable for those who use C
or Java.

Well... C# does have a couple of features not found in VB.NET, but they're
relatively minor (i.e. the XML Help documentor).

And as far as that particular example is concerned, temporary until we get
VB 2005.