Another C# article: "C# (C Sharp) Part 2: Plugging Into The .NET With MSIL"

Jon -

Thanks for the update. I'm not sure you've thought through everything yet,
but at least you've gotten more facts. Regarding:

"The Java platform supports only the Java language; .NET supports only MSIL,
but which can be generated by an unlimited number of higher-level languages,
including C#, Visual Basic, even Eiffel and COBOL."

You do realize that since Java is bytecode interpreted, any front end
language can be used to generate those bytecodes -- even VB. That no one has
seen an advantage in doing this, doesn't mean the platform can't do it.

- Jim

Jim VanHook <hook@removethis.omtool.com> wrote in message
news:397f3a62$1@news.dev-archive.com...
> Jon -
>
> Thanks for the update. I'm not sure you've thought through everything yet,
> but at least you've gotten more facts. Regarding:
>
> "The Java platform supports only the Java language; .NET supports only
MSIL,
> but which can be generated by an unlimited number of higher-level
languages,
> including C#, Visual Basic, even Eiffel and COBOL."
>
> You do realize that since Java is bytecode interpreted, any front end
> language can be used to generate those bytecodes -- even VB. That no one
has
> seen an advantage in doing this, doesn't mean the platform can't do it.

I did think about that, actually, before posting the article. But
truthfully, the Java VM was built for the Java language. It might be able
to run other languages, but it won't support them. "Support" goes deeper
than just being able to execute stuff. :)

Point taken, though.

Jon

Jeffrey Richter, a MSDN columnist, a consultant worked for MS NGWS project
has a forthcoming book on NGWS Programming. 3 of its' chapters was given out
in PDC.

The more I read it, the more I feel that .NET concept is basically JAVARIZE
everything after
all the marketing stuff and technical detail. These whole namespace plus IL
(right, not
bytecode, what's the big deal) language, none registry deployment have been
just what
others being done for years. The only bonus I guess is this
assemblies/manifest which
self describe an EXE.

COM is legacy now. VB has been gear up like Java. ASP+ is then VB/VBS +
HTML + some tag, I can see where it goes, something like JSP, one of the
counterpart of ASP but from Sun/IBM. Even ADO+ is not OLEDB based anymore
(correct me here).

The sad part is again we realized (proved by .NET) that MS has used entire
industry
for their technology conceptual beta testing for years (hint, OLD, COM, VB),
we just
cannot resist to fall in their trap again, thanks to MS's superior
productivity and marketing.

I guess nobody is perfect, so is MS.

"Jon Davis" <jond_123@REMOVE.ME.yahoo.com> wrote in message
news:397ea948@news.dev-archive.com...
> I earlier "spammed" a few Usenet and Microsoft newsgroups with a link to
an
> article I had written regarding C#. I discovered that much of the article
> was inaccurate, and after doing further research and questioning I have
> posted a follow-up article. Forgive me, but I felt the need to set the
> record straight.
>
> http://www.planetspooge.com/Programming/articles/-csharp2msil.htm
>
> Thanks,
> Jon
>
>