| > As far as I know at least ASP.NET MVC will run on Mono ASP.NET (MVC or classic) is not efficient on Mono, the pipeline is too heavy, and Mono (at least until 2.8 / 3.0 is released) leaks memory if you're not careful with the object allocation patterns you're using, since the GC is conservative ... and of course ASP.NET leaks memory. Mod_mono even includes a setting for automatic restarting of the Mono server, which kind of sucks. See http://www.mono-project.com/Mod_mono Async I/O is built around async sockets in the Windows kernel, and as such the API couldn't be implemented efficiently on top of poll/epoll. See this thread which is fairly recent: http://lists.ximian.com/archives/public/mono-devel-list/2010-January/033814.html
ASP.NET (both MVC and classic) is designed for usage in an IDE ... and you shouldn't ignore this point. For references, compare the experience of using JSF / Struts2 to the PlayFramework.It's practically the reason Java/.NET programmers say they can't live without IntelliSense, and Python/Ruby programmers are saying they can live just fine ... the difference it's in the design of those sucky APIs you have to use with Java/.NET I also haven't heard of any web apps that are running on Mono, and if there are apps out there, pretty much nobody heard of them ... so this whole argument is a myth. |
Initial benchmarks showed that the performance isn't that great compared to the same application running on Windows, but compared to similar applications on rails and django show that performance is comparable, even better than the dynamic frameworks (which is somewhat obvious since it's compiled).
Haven't profiled for memory leaks though.