Slashdot Mirror
Mono Project Releases Beta 1
AArnott writes "Ximian has just released beta 1 of its open-source implementation of Microsoft .NET platform. Mono allows .NET applications to run on Linux, Mac OS X, Unix, Windows. Mono 1.0 is slated for release on June 30, 2004."
sjanes71 adds "The first 'beta' always gets heaps of attention, and this is the first of three planned for the Mono project. Some of the new features touted for this release that updates Mono v0.31 include a faster interpreter, a global assembly cache, support for the StrongARM and HPPA platforms, generics support in the VM and C# compiler and an early alpha of System.Windows.Forms. C# and .NET is Microsoft's answer to Sun Microsystem's Java platform and Project Mono aims to create the Open Source, cross-platform version of Microsoft's new development environment."
You might also want to check out MonoDevelop v0.3 which was released to take advantage of new features in Mono Beta1. .NET development in Linux and rival VS.NET in Windows.
While it's not quite up to the task of stable work yet, it will become a great IDE for
For this it states:
Get off my lawn.
Microsoft open? Hah! .NET for mac or linux? (I mean the ms created version and not mono)
Where is
Their XML is a joke, swaths of proprietry code and an arsenal of patents to defend it.
Microsoft pays lipservice to "open standards" to keep the DOJ at bay, but after that it's business as usual.
Great work on Mono guys, we can only hope that microsoft won't dare use their patents against the project.
If it's just the IDE you're missing (and I wasn't aware that the Mono people were writing one), then you might want to take a look at icsharpcode.net. One of the projects (#Develop) is a free-as-in-both IDE for .NET.
In addition to that, Borland have a personal edition of C# Builder available, which is free as in beer, but not licensed for commercial use.
It's official. Most of you are morons.
These are my 0.02 US$...
...and that's about all they're worth.
.NET compatibility. Microsoft have always gone out of their way to make sure their new versions of Windows run software written for previous versions: do you know why? Because big business won't let them break things. Why should that be any different today than it has been for the last fifteen years?
According to your predictions for Mono, Microsoft should have litigated Samba into the ground years ago. Remind me, how many lawsuits has MS filed against Samba? Oh, that's right, ZERO . Not a single fucking case. Man, that bodes ill for Mono, doesn't it!
Of course the Samba team didn't get any support from Microsoft. But Samba still exists, and it still works.
Likewise, Microsoft can't break
And even in the case that MS do break compatibility... why should we care? Will that mean that Gnome apps using Mono and GTK# will suddenly stop running on Linux? Of course not. We'll still have something cool of our own.
Haha, far from it.
.NET developers interested in how the technology works.
.NET is something more than a new API for windows...
Choice quotes from the MS website:
It will be of interest to academics and researchers wishing to teach and explore modern programming language concepts, and to
Notice that nowhere in the list of intended uses is "Development", that's because it lacks all the libraries needed to make it useful.
This software was last updated 18 months ago - it's not undergoing development.
Simply another ploy to gull people into thinking
'm sorry, but WHAT THE HELL ARE YOU TALKING ABOUT? If you do .Net development in Windows, you use VS. You have no alternative. It's not "not a lot of fun", it's impossible.
.NET Framework Software Development Kit (SDK) version 1.1 includes everything developers need to write, build, test, and deploy .NET Framework applications--documentation, samples, and command-line tools and compilers.
Wrong:
The Microsoft®
The sub-classing of standard classes has been managed successfully in Java for many years. I've never had the problem where a new version of a class has produced a method with a name the same as one I might have written in a sub-class. Anyway, even if it did happen, the likelihood of it causing a problem is very remote. Java very easily distinguishes between (For example) Method(String string) and Method(boolean flag).
.NET libraries is that they aren't very extensive (Well, at least not when compared to the Java standard libraries). Of course to work around the limitations of the standard libraries we look for 3rd party libraries. In the case of Java, 3rd party libraries are mostly GPLed and free, where 3rd party .NET libraries are almost always commercial products with fees attached to their licensing.
Another thing I've found extremely prohibitive with the standard
Free Firefox news reader.
Chill. If Mono only implemented the CLI and a C# compiler, it WOULD be "just an open source implementation of the CLR/C#". But Mono implements nearly all of the MS.NET base class libraries as well. Those libraries are not part of the CLI. Therefore, the only accurate way to describe Mono is to say it implements .NET in Linux.
Shut up.
I'm guessing that DOS Plus imported a bunch of features from the Atari ST version of CP/M 68, which also looked just like MSDOS to end users (and was renamed TOS and had GEM as the UI.)
QDOS was a semi-clone of CP/M, built to deal with the fact that DR took their time to port CP/M to the 808[68] architecture. The original author denies it was a straight clone pointing out it had some nice features and architectural differences that weren't present in DR's OS, but there's no denying the API was intended to make porting CP/M programs easier.
CP/M itself dates back to the mid-seventies, with Dr Gary Kildall writing a crude filesystem and CLI for early Intel 8008 evaluation systems. CP/M 1.3 was practically unusable. CP/M 2.x became an industry standard, but was very tied to the architecture of those original Intel evaluation systems (CP/M required OEMs develop a BIOS that was practically identical to the firmware in those systems.)
So what you essentially have is:
(Mid seventies) CP/M for the 8080
1980/81: QDOS developed independently by Seattle Computer Associates, with many ideas taken from CP/M and with compatability in mind.
1981: Microsoft buys QDOS, releases it as MSDOS 1.0. IBM bundles it with PCs.
1981: DR releases CP/M 86 as a seperate product, this is essentially CP/M ported warts and all to the 8086. Nobody buys it.
1982: Microsoft makes dramatic updates to QDOS, releasing MSDOS 2, which has a proper file system, I/O redirection, all the things, essentially, we consider part of DOS today
1984: DR releases CP/M 68 for Atari. This includes an MSDOS compatable file system and many MSDOS APIs
1984: DR releases CP/M 3 (CP/M Plus) for 8080 based machines. Amstrad in the UK is only major buyer. This is still straightforward CP/M, antiquated file system and all, but with support for paged memory and with a lot more userland tools.
1985: DR releases DOS Plus. Amstrad, in the UK, is virtually the only major buyer. DOS Plus is mostly, but not entirely, compatable with MSDOS. Most people avoid it because of this.
1986 (I think): DR releases DRDOS. DRDOS is now almost completely compatable with MSDOS and begins to take off.
You are not alone. This is not normal. None of this is normal.
They are shipping both CLS and Microsoft compatible implementations. The basic idea is that new applications for Linux can use CLS plus the Mono stack (i.e., UNIX/Linux intended assemblies, like gtk-sharp, various DB libraries, POSIX wrappers, etc) and legacy or cross-platform apps can use the Microsoft stack (Windows.*, ASP.NET, ADO.NET, etc).
;-)
For example, a GNOME app written in C# for Mono would not use the Microsoft stack at all. So even if Microsoft broke/changed/patented the Microsoft (non-ECMA) stack, that would have zero effect on the tons of Open Source/Free Software apps developed using the ECMA and Mono assemblies. Thus, Mono provides both a great set of languages (C# and anything else that can run on the CLR), a good solid runtime (Mono+CLR stacks), an efficient and cross platform interpreter and JIT/AOT compilers, and so on.
The only thing Microsoft can kill is Microsoft compatibility. Which really isn't all that interesting to most FOSS developers.