Take a mix of the Java VM and the old "VB runtimes",
add some steroids and mass quantities of man-hours,
stir, simmer...
No you aren't wrong, it's just not the whole story.
My impression is that MS did with CLR for developers what they did with the
Windows interface for end-usres; taking lots and lots of feedback from one
side while trying to keep a consistent vision from the other. Not a fun
balancing act. And hell yes they tried to run over Java while making the
drive ;-)
Personally I *like* C#... it's a kinder gentler C++.
On 4/5/07, Rick Glazier <[EMAIL PROTECTED]> wrote:
Would it be too much of a stretch to say it was the "new" MS answer
to JRE (JavaVM) after they (effectively) got kicked out of that?
(Sorry if I got the wrong idea somewhere...)
Rick Glazier
From: G.Waleed Kavalec
clipped: >.Net is all about the creation of a layer that holds the most
common
>functions and services needed by any application; the implication is that
this
>layer will over time/versions become part of the operating system in MS's
case.
--
--
--
G. Waleed Kavalec
-------------------------
This email message is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not an intended
recipient of this document, please notify the sender, delete it and do not
read, act upon, print, disclose, copy, retain or redistribute it. In fact it
would be best all around for you to burn your computer then report to the
nearest office of the Department of Homeland Security and turn yourself in
as a potential danger to the moral fabric of America and a serious risk to
the purity of apple pie. If you actually are an intended recipient of this
document you are probably far worse than that and had better be making your
escape because appropriate authorities have already been notified. We know
where you've been.
