c# embodies OSS; java CSS

  • Thread starter Thread starter Popeye 'Bailo' Doyle
  • Start date Start date
P

Popeye 'Bailo' Doyle

Many have called for Sun to make java OSS

They declined

Now c# shines

On open language, that embodies the OOP paradigm

And meets the criteria of multiplatform, OSS

go mono

go dotgnu

Microsoft's legacy will be .net

In the same way that a dying corporation like Xerox gave us the mouse,
the GUI and the LAN.

Microsoft Research gave us a last swan song; so that even if Microsoft
fails and dies, .net and c# will live on -- as the Linux development
platform of choice !!!
 
In comp.lang.java.advocacy Popeye 'Bailo' Doyle said:
Many have called for Sun to make java OSS

They declined

Now c# shines

On open language, that embodies the OOP paradigm

And meets the criteria of multiplatform, OSS

go mono

go dotgnu

Microsoft's legacy will be .net

In the same way that a dying corporation like Xerox gave us the mouse,
the GUI and the LAN.

Microsoft Research gave us a last swan song; so that even if Microsoft
fails and dies, .net and c# will live on -- as the Linux development
platform of choice !!!

Take the C# trojan into the Linux citadel - and see what it hatches into.
 
There is a dire need for a modern framework / managed code based
language now that Linux is moving to the desktop. This is the reason
for IBM pushing Sun to opensource Java; remember IBM has a stake in
Novell who own Ximian who develop Gnome and Evolution IIRC. Ximian are
also developing Mono the C# / .Net clone. So the threat is clear,
opensource java or an alternative will be chosen that will not be to
Sun's liking but will fill a need.

The disucssion on the pros and cons of opensource vs the JCP miss the
point. Gnome developers, packages such as Debian etc. will not ship
something that is not based on opensource period.

We are at a crossroads, one modern language will become the basis for
development on the Linux desktop. It is upto whether Sun will
opensource java as to whether java is it, if not then ultimately on the
desktop the alternative chosen will usurp java.

Wake up and smell the coffee Sun!

Interesting articles on this here; http://ometer.com/desktop-language.html

KJP
 
I'd be happy to see C#/Mono prosper, but I'd rather see Java open
source. I am already very familiar with java and I like the language and
many of the APIs. But if Sun isn't interested in making Java open source
then C#/Mono can easily provide what we need.

If Sun loses in Linux then i suspect that they will lose in MS Windows
and Unix and possibly Mac OS X too; that would probably result in Java
falling into decline and becoming a 'maintenance language' for existing
Java applications only.

Losing Mind share is the danger for Java here. If C# gains mind share in
the Linux community then C# will come out the winner. C# already has a
significant foothold in the MS programming community.

- talk is cheap, worth about 2 cents i reckon ;-)
altkey
 
There is a dire need for a modern framework / managed code based
language now that Linux is moving to the desktop. This is the reason
for IBM pushing Sun to opensource Java; remember IBM has a stake in
Novell who own Ximian who develop Gnome and Evolution IIRC. Ximian are
also developing Mono the C# / .Net clone. So the threat is clear,
opensource java or an alternative will be chosen that will not be to
Sun's liking but will fill a need.

The disucssion on the pros and cons of opensource vs the JCP miss the
point. Gnome developers, packages such as Debian etc. will not ship
something that is not based on opensource period.

We are at a crossroads, one modern language will become the basis for
development on the Linux desktop. It is upto whether Sun will
opensource java as to whether java is it, if not then ultimately on the
desktop the alternative chosen will usurp java.

Wake up and smell the coffee Sun!

Interesting articles on this here; http://ometer.com/desktop-language.html

KJP

Indeed, that article is very interesting... Though there are some
technical errors, in regards to the .NET platform. For example, he says
he thinks it maybe impossilbe to implement Perl on top of it. In fact,
there is already an existing Perl (and Python) implementation. See,
ActiveState's web site for more information. Currently, there are some
20 plus available compilers running on top of the .NET platform. Every
thing from Smalltalk and Eifel to Cobol and Fortran.

I agree that Mono may have a few legal issues. I think their main
problem is implementing the proprietary classes of the .NET framework
rather then sticking with the ECMA/ISO standards. But, I saw an email
on the mailing list not to long ago that seems to imply that Novell is
in the process of addressing this issue. Basically, they are planning
to do a complete patent review prior to the release of Mono 1.0 and
split mono into to pieces - an ECMA/ISO stack and a non-ECMA/ISO stack.
They are going to remove dependencies of the Mono specific stuff on the
non-ECMA stuff (such as the GTK# using classes from
System.Windows.Forms).

Doing that may go a long way to encouraging acceptance of Mono. Despite
what people here may think of MS, .NET is a great platform for
development. It addresses a lot of issues that Java, IMHO, makes much
more difficult. With Java, you have to step outside the language to
interact with legacy code and systems - via JNI. C# defines as part
of the core specification a method of interacting native code as part of
the C# language. For instance, I have in my spare time (which I haven't
really had enough of lately) been working on a C# wrapper for the curses
library (and yes, when done I plan to release it under an open source
license - though it will probably be X11 or BSD as that is the license
that most of the Mono class libraries are under). This is fairly straight
forward under C# - but would be more difficult under Java - though not
impossible of course.

Personally, if the patent issues can be worked out - I think that Mono
or dotGNU would be a great boon to the Linux desktop. First, it would
solve the problem of ABI incompatabilities, by abstracting the interface
(something that Java is also capable of). It would allow almost all of
the common languages (including C++, since there is work being done
right now to standardized the Managed C++ extensions) to continue being
used without forcing all developers into a standard mold. I admit that
that can also be accomplished with Java - in fact there are already some
compilers for other languges that compile to Java byte code. Still I
think .NET will have an advantage here, since over the next couple of
years I expect that there will be a great deal more desktop development
done with .NET then there has been Java, simply because of the shear
size of the MS market share. Having a means to develop and deploy
applications across a broad range of architectures (Mono runs on
Windows, Linux, MacOS X, FreeBSD, and SPARC - they are realeasing the
initial JIT engine for SPARC soon, though the interpreter has been
available for some time) is very attractive.

I have to say, that as much as I like Mono - I don't believe that they
have a snowballs chance in hell of being successful. The main reason -
the Linux community will surely never accept any technology that came
from the "great satan of the northwest". Not that I fully blame them,
especially as long as the patent issues loom like a big, black cloud...
Still, I'm not sure that even if the patent issues did not exist that
Mono would ever be successful. Which is a shame - it is actually quite
a good and useful technology that would bring a lot of benifits to
Linux.
 
Many have called for Sun to make java OSS

They declined

Now c# shines

On open language, that embodies the OOP paradigm

And meets the criteria of multiplatform, OSS

go mono

go dotgnu

Microsoft's legacy will be .net

In the same way that a dying corporation like Xerox gave us the mouse,
the GUI and the LAN.

Microsoft Research gave us a last swan song; so that even if Microsoft
fails and dies, .net and c# will live on -- as the Linux development
platform of choice !!!

Are you trolling? I might admit that I partially turned into someone like
that CEOs with ideas. "If this wasn't tested 6 years stay away from it"
Especially if it comes from mickerosoft.

Spliting resources between many projects isn't nice idea, you should know
it. If C# applications would be on Windoze, it wont help Linux at all. See?
Applications would be on Windoze. They *M*A*Y* be on Linux too, but users
would stay where they were.
Personally I can create list on what should be absolutelly necessary for
Linux developers to do in next 2 years, if they would like to have chance.
They would need to do much faster than 2 years. 2 years was deadline for
well tested product nicely documented and STANDARDIZED.
Accidentaly it has nothing to do with a C#.
 
Raghar wrote:

Personally I can create list on what should be absolutelly necessary for
Linux developers to do in next 2 years, if they would like to have chance.

Then you should absolutely do that and post it.
They would need to do much faster than 2 years. 2 years was deadline for
well tested product nicely documented and STANDARDIZED.
Accidentaly it has nothing to do with a C#.

The problem is: the customer is getting used to having a OO layer for
manipulating the OS, and Web tools that bridge the gap between traditional
client programming and web programming. Java does not do that well.
c#/.NET does.
 
Many have called for Sun to make java OSS

They declined

Now c# shines

On open language, that embodies the OOP paradigm

And meets the criteria of multiplatform, OSS

go mono

go dotgnu

Microsoft's legacy will be .net

In the same way that a dying corporation like Xerox gave us the mouse,
the GUI and the LAN.

Microsoft Research gave us a last swan song; so that even if Microsoft
fails and dies, .net and c# will live on -- as the Linux development
platform of choice !!!

..NET wasn't Microsoft Research's baby. It was Microsoft's Developer Tools
Division - and mostly Anders Heljsberg at that, with some guys from the
COM+ team.
 
Milo said:
.NET wasn't Microsoft Research's baby. It was Microsoft's Developer Tools
Division - and mostly Anders Heljsberg at that, with some guys from the
COM+ team.

Great, you can write their bio in the /History of Computing/ publication by
Novell.
 
Back
Top