Date: Thu, 24 Dec 2009 12:03:36 -0800
Reply-To: Savian <savian.net@GMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Savian <savian.net@GMAIL.COM>
Subject: Re: Slightly OT Java vs. C# crosspost from Perl
Content-Type: text/plain; charset=ISO-8859-1
On Dec 24, 9:01 am, jgoldb...@BIOMEDSYS.COM (Jonathan Goldberg) wrote:
> The issue isn't, to my mind, C# vs Java; there is IMHO really not much to
> choose between them. Both represent OO technology at about the same stage
> of development.
> The issues is see are two:
> 1) Run-anywhere vs .NET. If you're willing to commit to MicroSoft
> then .NET, including LINQ, in very powerful. (Alan introduced me to LINQ.
> I agree with him about how good it is.) Are the Java libraries as good?
> MicroSoft goes for power rather than simplicity. SAS has always done the
> same. I think the last people on earth who were actually willing to
> sacrifice power for simplicity were Dennis Ritchie and Ken Thompson, who
> designed the C programming language.
> 2) SAS has committed to Java. There is a Java Object; there is no C#
> object. Considering how multiplatform SAS is and C# isn't (C# on the
> mainframe?) I'm not sure that's going to change. OTOH, I'm also not sure
> how much the Java object is actually used. I've never used it.
SAS is committed to .NET and C# in EG and AMO.
.NET can also be run in Linux but it is defintely a Microsoft
technology. .NET 4.0 rocks, BTW, especially when you deal with Office