-
Website
http://tirania.org/blog -
Original page
http://tirania.org/blog/archive/2008/Oct-06.html -
Subscribe
All Comments -
Community
-
Top Commenters
-
Max "WorldMaker" Battcher
7 comments · 1 points
-
psantosl
18 comments · 1 points
-
whitemice
8 comments · 1 points
-
barrkel
6 comments · 3 points
-
Ed Ropple
27 comments · 13 points
-
-
Popular Threads
-
C# String Interpolation - Miguel de Icaza
3 days ago · 59 comments
-
Cena Linuxera en el DF, hoy - Miguel de Icaza
8 hours ago · 3 comments
-
New Moonlight Covenant has been posted - Miguel de Icaza
8 hours ago · 2 comments
-
Nine Months Later: Mono 2.6 and MonoDevelop 2.2 - Miguel de Icaza
1 week ago · 43 comments
-
Releasing Moonlight 2, Roadmap to Moonlight 3 and 4 - Miguel de Icaza
5 days ago · 30 comments
-
C# String Interpolation - Miguel de Icaza
¡Saludos!
La Paz. B.C.S México.
kudos to everyone who was involved!
Oh, and there is no Mac installer yet... ;-)
Yeah, we are sorry we could not get to do the packages for MacOS on time, they will come out this week.
Congratulations!!! I'm really excited to see a new version coming! Mono only goes stronger release after release!!
Will it be official packages for Solaris and BSDs?
But what you guys did is quite amazing. You should be proud!
Congrats!
I've read developers can use SlickEdit when moving to Linux to develop Mono code. Is there any kind of support for that?
I remember setting it up a few months ago and it is possible to build projects from SlickEdit, even get the build errors, although by that time it was unsupported by SlickEdit... (It was possible, but on your own)
This means that we are trying to work with the Debian packagers and experts on packaging Mono on Debian; Solaris packages to do the Solaris packaging and so on.
There is a new mailing list for this: mono-packagers-list@lists.ximian.com
In the meantime, you would have to compile this yourself from source
Pero soy un poco triste que no hay soporte oficial para distribuciones basadas en Debian (¡ y hasta Enero de 2007 se reportaron 129 distribuciones basadas en Debian!). En Ubuntu la versión actual todavía es 1.2.6 que es más viejo que Matusalén. ¿ Por que no hay ningún soporte para distribuciones basadas en Debian ?
A mí no me gusta mucho el diseño nuevo de sitio web de mono. El diseño viejo era mucho más amable y tenía un diseño mucho muy distintivo.
Saludos al equipo de mono y otra vez muchas gracias por el trabajo maravilloso.
PD: Miguel, en la lista de compiladores de código abierto has olvidado a "Nemerle".
Estamos trabajando directamente con los empaquetadores de Debian para asegurarnos que ellos le den el mantenimiento adecuado a Mono en Debian.
Hay una lista en http://lists.ximian.com con la ifomracion.
At the least a tarball of the binaries would be good - I don't think there should be anything significant in the installer that really needs admin access.
thanks,
Ian
https://bugzilla.novell.com/show_bug.cgi?id=414209
We are lagging a little bit behind on the 2.0 release (Mac packages are not up yet for example), but we will get to this as soon as the other bits are done.
Specific questions to answer include; Do I have to jailbreak my phone? Will Moonlight work in the browser? Will Cocoa# work with the UI?
TIA
queda felicitar a todos los que han puesto su sangre y sudor en el proyecto.
gracias.
Each version just gets better and better and i am always anxious to see the next one. I hope i can try out this version soon without recompiling the sources myself and fixing missing dependencies (i am using Ubuntu and at the moment there is no newer version of mono available, for getting mono 1.9 i used the installer version which worked just fine, but a simple sudo apt-get install would be nice). It's great to see that the C5 Generics Library, the Visual Basic 8 compiler and the new mono debugger is included in this release.
I'm eager to see whether the performance increased in the new version since i am doing a lot of graphics programming with mono/.net and the excellent tao framework shortly (something which was only possible with C++ recently and now is doable with mono). I still measure a substantial performance difference between .net and mono (depending on the operations) but it gets less and less with each version which makes me very happy and confident.
Do you know when mono will be shipped out with linear IR and the generational garbage collector ?
Off-Topic: What happened to the mono site ? It's now looks so gloomy. Where is the nice and cheerful Monkey-Jungle Theme gone ? Being a primate i miss all the monkey pictures and my jungle ;-) And the monologue page still has the old style ...
Again many thanks to you and the rest of the mono team for this great new release. It is a great piece of work and i hope you will keep going.
Cheers,
Berti
Mono already features ahead of time compilation (see Miguels blog http://tirania.org/blog/archive/2006/Aug-17.html ) as does .NET with ngen. But code generated with that is not faster (since it is position dependent) and can even be slower (only startup time is faster). And that is even the case for GCJ !!! It might sound strange but gcj most often is slower (!!!) than the newest java sdk versions.
(for a speed comparison between gcj and java see http://shootout.alioth.debian.org/gp4/benchmark... )
I myself thought for a long time that code running in a virtual machine can not be executed as fast as native code. For highly optimized C++ Code this is still true and that might even hold until the end of time. But since i am not doing the usual .NET, ADO.Net, ASP.Net stuff with mono (the bread and butter stuff of the majority of companies) and do a lot of prototyping of algorithms which work on a lot of data and do a lot of number crunching instead, i have a good feeling about the speed of various implementations of languages.
Six years ago i started doing some benchmarking with raytracing and mesh algorithms in C# and C++ and compared the running time of the implementations. The result was a catastrophy. C# was about six times slower than C++ (but i have to admit at that time i had nearly no knowledge of how to program C# efficently :-) ).
Nowadays when i compare the running time of a standard not highly optimized C++ program and it's counterpart in C# i get results that show, that the C# solution reaches about 75% up to 90% of the C++ version under Microsoft Windows with .NET 3.5
(of course using SSE-Intrinsics and using everything C++ might have to offer, you might even be faster, but that alone opens possibilities which i never dreamed of)
And if you compare the quality of the code generated from the Mono C# compiler with the code generated by Visual Studio 2008 you will see that it is from a performance point of view equal. That means that the mono team has done an outstanding piece of work which they can really be very proud of. Their compiler is as good as the newest Microsoft compiler. That means, if you run a mono compiled executable on windows you won't see any difference to a Visual Studio compiled one, which is marvelous.
The code generated by the jit is still somewhat slower. From my measurements it is about 50% up to 66% of the speed you will get on .NET 3.5 on windows which is acceptable if you think about the other work the mono team has done.
The first priority for the mono team surely is api completeness, because most companies need mono for porting their Windows ADO.NET, ASP.NET application to Linux and that is clearly more important and has a higher priority. First make it work, then make it fast. And if you think about the development of gnome applications then mono applications are really a lot faster than the usual gnome python based applications (i love python and use it a lot, so nothing bad against it, but it really is noticeable slower)
But what i have seen is also, that mono gets faster and better with every release. And i am very sure that, when they have linear ir and the generational garbage collector ready the mono guys will rock .NET even more than they have done in the past.
So just wait anxiously for the next releases and you won't ask for static nativ code again :-)
They have done a great job and i am sure they will do so in the future.
Berti
It's sad that you invest time in supporting all these distros, when some people just want to get the binaries!
I even don't need an installer, but a simple tgz with all the binary files...
I always download it and strip it to the minimum for our Debian based devices. I'd really like to get it now, but was completely lost in all the rpms...
(I just wanted to extract the raw files from them)
It's not a nice experience to see pages that tell me to use update-manager I never heard of!
And there was no progess in the download server since 4.10.
It would be great if there was some progress... I don't even need any installers, I know that this is work, but just a bare download of just the binary files (I don't want to compile it myself).
Also it was confusing that somehow 1.9.2 seems to be an RC for mono 2.0???
Were is that fork?
Well, maybe it clears itself up shortly, great release, mono is simply great!! Being really open, flexbile, fast, nice to use and bringing some good things from windows to liunx making them so much better! I love it!
What is the best way to learn Mono?
After that you will be there..
In the past our RPMs ended up conflicting with distribution-provided packages, or in the case of Debian, our packages had a very different partitioning than what they used.
We are now working early with distribution maintainers to ensure that relevant patches are applied upstream and that they get the source for their packages on time.
It is a transition period, but the end result will be a better distributed Mono fr everyone.