Linked by Thom Holwerda on Wed 3rd Oct 2007 19:39 UTC, submitted by gonzo
.NET (dotGNU too) "One of the things my team has been working to enable has been the ability for .NET developers to download and browse the source code of the .NET Framework libraries, and to easily enable debugging support in them. Today I'm excited to announce that we'll be providing this with the .NET 3.5 and VS 2008 release later this year. We'll begin by offering the source code (with source file comments included) for the .NET Base Class Libraries, ASP.NET, Windows Forms, ADO.NET, XML, and WPF. We'll then be adding more libraries in the months ahead (including WCF, Workflow, and LINQ). The source code will be released under the Microsoft Reference License."
Thread beginning with comment 276009
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: holly...
by PlatformAgnostic on Wed 3rd Oct 2007 23:00 UTC in reply to "RE[2]: holly..."
PlatformAgnostic
Member since:
2006-01-02

Or you could use .NET/Mono because it is likely to be a better runtime since it has the benefits of lessons learned from the Java experience. And having competition allows both platforms to evolve faster.

Reply Parent Score: 3

RE[4]: holly...
by TemporalBeing on Mon 8th Oct 2007 19:39 in reply to "RE[3]: holly..."
TemporalBeing Member since:
2007-08-22

.Net is not any better than Java except in that it is tied to a single platform (Windows) and can therefore make certain optimizations that are otherwise not available.

It is a lot easier to design something for a single platform/API/processor than it is to try to do what Java does.

.Net has a bit better performance as a result, but it lacks the ability to move stuff between systems - yes, even with Mono which will never be as complete as Microsoft's .Net implementation is. So your comment is quite a bit off the ball.

Reply Parent Score: 1

RE[5]: holly...
by PlatformAgnostic on Tue 9th Oct 2007 02:31 in reply to "RE[4]: holly..."
PlatformAgnostic Member since:
2006-01-02

I'm not seeing how you get this idea. The .NET class library is tied to Windows, but there is more effort involved in porting the VM runtime between x86, x64, and IA-64 than to other OSes. The VM also runs on ARM.

The singular area in which I could imagine .NET having a performance advantage over Java from being tied to Windows is in exception handling. Java has to be able to deal with Signals from UNIX and SEH in Windows. But SEH isn't exactly a performance winner and exceptions are... well, exceptional. The underlying OS is not very important to the performance of compiled code except insofar as it calls down to the OS for I/O and gets interrupted by the OS for scheduling and page faults.

Sure, Java has the explicit goal of being portable between OSes. This fact doesn't prevent Java vendors from writing highly-optimized libraries and runtimes for specific OSes. And they do so. Even Microsoft wrote a JVM that was well-regarded for its performance. .NET is simply an incremental improvement with the lessons of Java in mind.

Reply Parent Score: 2