I'll reply just to the incorrect data about mono, unless the folks here want me to expand further, since I guess talking about the real advantages of mono would be more appropriate in a mono list.
On 03/09/06 [EMAIL PROTECTED] wrote: > Now your Questions: > [1] What advantages does DotGNU offer over Mono? > As we started, we tried Mono too. But we were not happy with monos > windows.forms implementation. You had to use the Wine emulation to get > the Windows.Forms. Mono used wine two+ years ago. Currently mono's Windows.Forms implementation works quite well. > Our app, still does not run on mono! Did you ever file a bug report? The Windows.Forms guys will be happy to fix the issues you are having. > The big advantage mono has, is the jit-compiler. BUT: the guys here > are working on jit too, and I hope we'll get it soon on DotGNU. The JIT is just one of the big advantages of Mono. Mono has also complete support for Reflection.Emit, Remoting, Generics and Appdomain, which allow mono to correctly run ASP.NET code, java programs through ikvm, python code using IronPython, other languages like boo and nemerle. Mono also has an extensive test suite. On 03/09/06 Marc Haisenko wrote: > I'd like to add: I don't how things look now, but back when Trumpf evaluated > Mono its System.Windows.Forms was only available on x86 systems because of > the WINE dependency, while dotGNU's System.Windows.Forms ran everywhere where Again, not true for a lot of time, now. In fact, some people who used to use dotGNU for it's Windows.Forms support, use mono now. > The Mono folks just don't have a focus on GUI programming, their focus is on > the server side. This is incorrect in many ways. If it wasn't for Mono's focus on GUI programming, we would have not developed Gtk# and the associated assemblies that allowed many new Linux GUI applications to be developed: tomboy, beagle, muine, banshee, monodevelop among them. Mono is a flexible runtime that allows us to run GUI apps from embedded systems like the Nokia 770 to common systems using Gtk# and other toolkits (like Cocoa on OSX). Of course mono works well also on the server, but this doesn't mean we neglected the GUI stuff, since it's clear we didn't. We of course focused first on Gtk#, because we are free software programmers and wanted to provide a nice development environment for programmers on Linux with the preferred gUI toolkit, but we also now support Windows.Forms for the legacy code people coming from a windows background may have. > In Mono you're not so happy. Things are very intermixed there. Granted, I Incorrect: we implemented libgdiplus and we have a driver layer to support win32, X11 and OSX windowing systems. > So if you need to do GUI development I'd recommend dotGNU to you. Mono's SWF > isn't as mature, and if you need to fix bugs you'll have a harder time to do > so in Mono as their SWF code is not so good, IMHO. Well, given your incorrect assesment of Mono's SWF implementation, it's clear you haven't seen much of the code. How about if, instead of personal opinions, you provide actual SWF programs that don't work or don't work well in mono? Missing that, my advice to you is to expose the advantages of dotGNU, instead of mudthrowing at mono. Besides, Mono's SWF is supported, so if bug fixing is needed everyone can just file a bug report. Thanks. lupus -- ----------------------------------------------------------------- [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better _______________________________________________ Developers mailing list [email protected] http://dotgnu.org/mailman/listinfo/developers
