Re: afraid of .NET

In comp.lang.java.advocacy, Oliver Wong
<owong@xxxxxxxxxxxxxx>
wrote
on Tue, 21 Mar 2006 15:51:52 GMT
<siVTf.5992$nQ6.673@clgrps13>:
"Paolo" <pronipaolo@xxxxxxxx> wrote in message
news:1142897420.198597.194750@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Now I am seriously afraid for Java future on the desktop.
When windows Vista will be available, with .NET preinstalled, with Mono
on every Linux distribution, I suppose even Mac will support it. At
that moment, who is going to use Java on the desktop anymore?

I wasn't aware that Mono was a "serious" API library yet,
though admittedly, I haven't been keeping watch of their
progress.

I for one find the Mono Developer rather crude compared to Eclipse.
However, I am also given to understand that Eclipse will support
..NET. I, however, could be wrong; Google is being reticent and
the Eclipsipedia (http://wiki.eclipse.org) seems to know nothing
about .NET.

Do they have GUIs working now, for example?

Gtk#.

<Does a quick Google Search/> Yes, I guess they do. And it
does look like they have some pretty good demos now. Is Mono
being bunlded with most Linux distributions too now?

Not sure about bundled, but it's available; certainly Gentoo
has it for download/build using 'emerge'.



Will .NET kill Java as Explorer killed Netscape?

Why the U.S authorities let microsoft destroy the competitors, just
because they have the monopoly in the desktop area?

Why does SUN does not understand that Java should be shipped freely in
every Linux box? Sun should make any possibile effort to convince the
PC manufacturers to ship Java right now and even after Vista, in my
humble opinion.

Instead Sun is fighting against Linux, it pays Gnome, which is
developed by who develops MONO! it's concurrent! Sun fights against
IBM, which spread Java in the enterprise.

Can anybody explain me the Sun strategy? Will Java die because of
.NET!? Should I download Visual Studio?

I'm assuming most of these questions are rhetorical.
I think if .NET really takes off, someone will write a
Java to .NET compiler.

Java#, presumably. Apparently Google hasn't quite twigged
onto the term 'Java#' yet.

My
understanding is that MSIL is fairly well documented,
and Java is relatively pleasant to write a lexer and
parser for (as opposed to, say, COBOL or C),

Java templates introduce a quirk, to be sure, but they're a lot
easier than with the C++ variety, from a parsing standpoint.

so it shouldn't be too difficult a task. The only problem
for Java developers at that point is learning a new set
of APIs, or porting over the existing API to .NET (perhaps
via the GNU ClassPath project).

- Oliver



--
#191, ewill3@xxxxxxxxxxxxx
Windows Vista. Because everyone wants a really slick-looking 8-sided wheel.
.

Relevant Pages