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
"koorb" <ko***@raidrs.co.uk> wrote in message
news:i9********************************@4ax.com...

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?

[Herfried K. Wagner [MVP]]

* koorb <ko***@raidrs.co.uk> scripsit:

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.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

[koorb]

On Sat, 4 Sep 2004 17:58:38 -0600, "Bob Lehmann"
<no****@dontbotherme.zzz> wrote:

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]

On 2004-09-04, koorb <ko***@raidrs.co.uk> wrote:

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]

koorb <ko***@raidrs.co.uk> wrote in news:i9jkj011l9dh8ku9t80chhab7r7nvf9sf8
@4ax.com:

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).
--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/

[Lucas Tam]

koorb <ko***@raidrs.co.uk> wrote in
news:df********************************@4ax.com:

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.

Some companies use VB.NET others use C#... and others use Perl.NET or
Delphi.NET.

However, assemblies built with any .NET langague are compatible with other
languages. Also, all languages should implement the full .NET API, so
language is really a moot point - just choose a language you're comfortable
with.
--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/

[Lucas Tam]

David <df*****@woofix.local.dom> wrote in
news:slrncjkr70.6pe.df*****@woofix.local.dom:

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.

Here's an interesting link with all known .NET langauges :

http://www.gotdotnet.com/team/lang/
Kinda interesting seeing how many .NET compatible languages there are out
there.

--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/

[Bob Lehmann]

How does .Net unify the languages? How would the job be finished? I thought
your premise was that the languages are not unified.

So, VB or C#, Vanilla or Chocolate, Ford or Chevy. What's your point?
http://tinyurl.com/694op
http://tinyurl.com/65gct

Bob Lehmann

"koorb" <ko***@raidrs.co.uk> wrote in message
news:df********************************@4ax.com...

On Sat, 4 Sep 2004 17:58:38 -0600, "Bob Lehmann"
<no****@dontbotherme.zzz> wrote:

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 arealso 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

[Cor Ligthert]

Koorb,

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.

This sounds like you take this as the standards from the in the history of
Eureope called middle ages when there where no inventions anymore done
because they where sure that things could not be done better.

Just my thought,

Cor

[Cor Ligthert]

I wrote an unreadable sentence
-----------------------------------------------
Koorb,

It sounds to me that you take the sentence Industries are built on standards
in a very narrow way.

The history of the middle age of the European history learns us that
Industries are broken down when there are no more inventions done.

Just my thought,

Cor

Koorb,

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.

This sounds like you take this as the standards from the in the history of
Eureope called middle ages when there where no inventions anymore done
because they where sure that things could not be done better.

Just my thought,

Cor

[Herfried K. Wagner [MVP]]

* koorb <ko***@raidrs.co.uk> scripsit:

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.

It's not the goal of .NET to /unify/ languages. .NET is the foundation
on which program execution takes place and the .NET Framework provides a
class library that /can/ be used by .NET programming
languages/applications.

There's even a compiler for Brainf*ck to MSIL available:

BrainFuck.Net
<URL:http://elswanko.vm.bytemark.co.uk/~fraggle/stuffage/bf.net/>

Notice that no change in the language's syntax was necessary to make it
compile down to MSIL. You cannot use any .NET classes in Brainf*ck, you
cannot create classes, but the compiler will still create .NET
applications.

So, unification doesn't take place on language level, it takes place on
execution/library level.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

[Jeff Johnson]

"Lucas Tam" <RE********@rogers.com> wrote in message
news:Xn***************************@140.99.99.130.. .

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).

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