Slashdot Mirror
Fedora Core 5 includes Mono
cyberjessy writes "Surprise! The Fedora Core 5 Release will include Mono in the distribution, in spite of Red Hat's opposition. In addition to the Mono runtime, it will also include Mono applications like Beagle and F-Spot. Is the Linux community finally ready to accept Mono? Mono is becoming increasing important due to Windows Vista, which has WinFX (the next .Net Framework) as its core API. This will mean that in future, all native Windows applications will easily run on Linux, with Mono. Will Mono achieve what WINE could not?"
Parent got it more right than you. WinFX is the next iteration of the .NET BCL which is a collection of managed APIs, including (that is, now adding) WCF (Windows Communication Foundation, formerly known as Indigo) and WPF (Windows Presentation Fondation, formerly known as Avalon) and WWF (Windows Workflow Foundation). XAML is the declarative (XML-markup) which is similar to XUL. All that can be done in XAML can also be done in code; elements used in mark-up will be immediately available as first class objects in C# and friends.
Something like this: http://www.cygwin.com/ ? :-)
And there's a ports site, too: http://cygwinports.dotsrc.org/ KDE, Gnome, Xfce4 and many apps. Very nice
There is a WinForms compatibility layer in the making. Its first release will handle the WinForms of the 1.1 .net specification. Mono will be forced to play catching up with this GUI framework and it uses the compatibility stack instead of the ECMA compliant one.
If you want to make Linux applications using Mono I strongly recommend using GTK#. Beagle and F-Spot use GTK#.
Cheers,
Adolfo
If anyone thinks that Mono will allow applications that were written on windows to the windows implementation of .net will somehow run seemlessly under linux, think again. .net is largely a scripting front end for native windows C++ dlls. Yes there are some implemenations of some of the .net libraries for mono but there is no way that 90% of the code written for .net will ever work under linux. Even applicatons written specifically for mono, like paperboy or beagle are shakey at best.
.net framework is useful, but if you want to get/write/use cross platform applications, say away from propietary M$ technology.
I suppose mono is interesting if you think the
The difference between Canada and the USA is that in Canada healthcare is a right and gun ownership is a privilege.
Not quite, Mono also includes a VM that interprets the .net bytecode, much like java.
Secure messaging: http://quickmsg.vreeken.net/
Well. If it was about running this or that app despite it being written in .NET, that would be all fine and dandy, but new and useful Unix/Linux apps are being written in C# as well. Take the desktop search Beagle for example, or the music player Muine. Some people just seem to like the language and the libraries.
Is this really true? I was under the impression that Cacao was actually fairly fast.
And the Mono runtime is far from wonderful at this point, IMO (not all that stable, and not particularly fast).
Throw the bums out!
People in Europe and Britain are kinda safe right now. Software patents are being granted, and are being used as the basis of litigation threats that the recipients can't afford to contest, but at least the courts are on our side, so far.
This situation is not stable. If China, India, and Latin America bring in software patents, then Europe will probably give in at a subsequent world trade agreement.
To keep people in Britain and Europe safe, people in Britain and Europe must take action - and one easy way to do this is to donate to competent, active groups such as FSFE. One way to do this is to join The Fellowship of FSFE, and also encourage others to join.
Here's a webpage about how and why to support FSFE's Fellowship campaign.
Please help publicise swpat.org - the software patents wiki
IMHO, dual boot is a pain. I prefer coLinux http://www.colinux.org/ :-)
And I think it runs on Linux, too
You can get it here and according to their website it will run on the following:
It is like Java, except that it is designed to feel and perform like a native windows app.
As for Vista. Considering the monumental effort that they made in making their
Cheers,
Adolfo
WinFx is not the next .net framework, it is the next generation API set.
It's an encompassing term, covering Presentation Foundation (how you display things on screen), Communications Foundation (secure program to program stuff), WinFS (the meta data "file system"), Workflow and Infocard (authenication and authorisation), all of which exposed as a managed code API.
It is also not limited to Vista, most of it will be back ported to XP and 2003. Look upon it as a Win32 replacement for .net. Now imagine implementing that from clean room code. Stop crying at the back.
So whilst the summary may be concise, it is not, I am afraid, accurate.
Let, me guess...you happen to think that portage is amazingly slow in doing anything right?
:)
Have you tried the 2.1_pre releases yet, a lot of effort has gone into improving the scalability of it. You will notice a vast improvement on most systems with it. Especially when you hit the KDE modular ebuild updates.
You can also feel free to visit any of the developers in the irc channels ranging from #gentoo to #gentoo-portage for portage itself on irc.freenode.net. Generally, we're all willing to have a nice talk about our various area's with the end user, after all we are end users as well.
ps. just don't start in with the rewrite it in C so it's cool and awesome and python sucks...that'll quickly get you disliked
The most recent time this was discussed by the wine developers is in this thread. At one time some Mono developers were linking wine to mono, but then they got upset about the changes in the Wine API for Linux programs (this was before the 0.9 release), and they decided to just do all WinForms-related stuff with native .NET code. AFAIK no one has tried to do anything in that direction since the 0.9 release.
Eclipse is a package in FC4, compiled with gcj. It's fairly stable, and the user-interface is the same as in a version of Eclipse running with Sun Java on another platform.
MainForm.cs(35,26): error CS0234: The type or namespace name `Windows' does not exist in the namespace `System'. Are you missing an assembly reference?
Also, C# 2.0 isn't complete, are you sure you shouldn't be using mcs over gmcs?
http://www.mono-project.com/CSharp_Compiler
Okay, there are several areas that .Net/Mono etc encompass. First, there is the core Common Language Runtime; this is what runs a given application. The CLR is well defined within the ECMA/ISO standards, as is most of (second) the core framework. Microsoft extends the core framework with ADO.Net (command data layer) Microsoft.* (VB Compatability objects and a few others), ASP.Net (web apps, and services) allong with SWF (Windows forms).
.Net, there are other areas it has that MS's framework doesn't include... By the same note, you could say similar things to C++ development, if doing GUI development. You don't get the MS libraries for windows development in GCC, but you can still create GUI apps that are portable.
Mono already has the core framework, as well as compatability for most of the rest... Some areas are indeed incomplete, but not in a way that inhibits current apps. Mono also includes several DB adapters that aren't inside the MS distribution, in addition to GTK# (for gnome/gtk based app development, which can be relatively portable to windows and mac), there are also a few other goodies on the mono side (Posix library, etc).
You *can* develop a portable application under mono without touching any of MS's extensions, and it can still be portable. Which is imho a good thing. There are other libraries for QT (kde), audio, opengl etc, some of the projects around them are stagnant, but usable. Mono isn't just a subset of
Mono is an implimentation of a standard, with some compatability to proprietary extensions, and including some extensions (F/OSS) of their own. In addition to many 3rd party libraries. For rapid app dev (RAD), it's really a second to none thing. You get a complete framework, bytecode portability both of these other frameworks offer. In addition to a key element, *MUCH* easier interaction with system libraries not part of the core framework. This is the kicker here, you can target system APIs *VERY* readily, making core functionality easier to do, than other managed environments.
I am no big fan of MS by any means, but to be honest, regarding patent litigation, they haven't shut WINE down, which is *FAR* more infringing than anything mono is doing, not to mention that under litigation they could strip the infringing parts and still have core functionality in place. There's a lot of prior art for anything ASP.Net does, how ADO.Net interacts, and the current winforms are dying (as far as ms marketting is concerned in favor of WinFX). Mono has been around for several years now, with no litigation in sight.
Michael J. Ryan - tracker1.info
Windows Forms are not bad, but they could be a lot better. Microsoft realized this and is introducing XAML as a replacement, and I am eagerly awaiting its arrival.
WinForms don't provide an elegant method for separating the View from the Controller. WebForms achieve this by having an aspx markup page that links to a cs or vb controller page. GTK does this by linking a glade XML file to a code file. In this sense, GTK is superior to WinForms.
XAML solves the issue of code and design separation using the same approach that WebForm and GTK use.
Cheers,
Adolfo
Has anyone considered the notion that Mono should be implemented because a Common Language Runtime is actually a good idea?
That's probably true, but approaches like PyPy and Parrot are probably going to be vastly superior in terms of both flexibility and performance (I'd bet on PyPy if I had to pick one right now--of course it only runs Python, Javascript, and a couple other languages at the moment, but it's got smart developers, serious European Union funding, and a design that lends itself easily to implementing other language front ends, and performance is improving at an incredible rate).
rage, rage against the dying of the light
Now, it seems the implementation is also pretty decent for cases where "people" is a normal .NET collection object ("deferred execution"), but still, decent OSS languages have had HOFs for years, and this isn't something that's particularly new or hard to do despite some PHBs who now start foaming on the mouth fantasizing how Microsoft is going to revolutionize the way we deal with data in programming languages...
You should read that information before making any comments about patent issues.