Manos de Mono: The Manifesto (.NET Web Framework)

http://jacksonh.tumblr.com/post/1159500924/manos-de-mono-the-manifesto

by eduardoflores • 16 years ago

76 22 16 years ago

jacksonh.tumblr.com

WorkerBee3• 16 years ago

One unanswered question:

What specifically does this project bring that isn't present in ASP.NET MVC, OpenRasta, FubuMVC or MonoRail?

Or that couldn't have been achieved by porting one of those to Mono (if they aren't there already)?

markkanof2• 16 years ago

I posed the same question to the author on his blog. As far as I know at least ASP.NET MVC will run on Mono, and I would bet the other frameworks would as well.

I'm all for any new tool that would make my life easier, but it would be great to hear what this framework is going to offer that isn't already offered in the other existing frameworks.

WorkerBee3• 16 years ago

How many frameworks is the right number? One is too few. One hundred is too many, it will just fragment people's skills.

Experimentation and inventing your own wheel is good for learning. But most of the time those wheels shouldn't see a wider audience - unless they have something new to offer.

bad_user4• 16 years ago

> 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.

eduardoflores2• 16 years ago

The offer in the manifesto is to be simpler. I'm not to judge since don't know all the other frameworks, but at least seems promising.

WorkerBee3• 16 years ago

You'd have to know all the other frameworks in order to know that yours is simpler.

javery2• 16 years ago

Just from reading through it quickly it includes the following things I believe are absent in all of the above (although I have only worked with ASP.NET MVC and MonoRail).

1) It has a built in web-server. This is hugely awesome, especially since it is based on Tornado. No mucking with Apache or Nginx, CGI, etc.

2) It includes command line app generation and compilation - missing from at least ASP.NET MVC.

3) Simple Routing - did you look at the route and lamba? That is awesome.

Some of what is here is similar to what exists, but this looks much improved. Pipes looks to be an improvement over the current HttpModules of ASP.NET. The view engine looks like an improvement over .aspx. The HTML5 template looks like an improvement over the crappy templates that MVC creates.

city41• 16 years ago

What happens if Tornado doesn't meet your needs? How easy is it to move this framework onto something else?

antileet4• 16 years ago

This seems to be what Flask is to Django and what Sinatra is to Rails (From a very brief amount observation). There's a huge trend to move into more "lightweight", "self-hosted" types of development.

After building a moderate sized application (currently around 5-6k LOC) in .NET MVC2, some of Jacksonh's decisions start to make a little sense. However, there are a lot of situations when a paradigm seems neat but in reality it might not be _that_ useful.

For instance you can respond to queries using Lambdas/Anonymous delegates like Get("/foo", ctx => ctx.response.write ("foo")); YAY! I made a HTTP Response in just one line.

But looking at about 17 different endpoints I have in my application, not one will benefit from this feature. In the current model, I may spend a minute or two defining an action and specifying the route, but will spend atleast half an hour implementing it. For some reason, everyone seems to be focussed on cutting down the two minutes to one minute.

Also, this means that the routes aren't in one place. MVC2 has named routes and I can quickly change things from a single function. I used to like Flask's technique of making routing easier by simply specifying the route as a function attribute/decorator - but this made maintaining it quite hard.

Also, this tries to do everything. For instance, it allows you to serve static files as well like -Route ("/Content/", new StaticContentModule ()); When I have something like nginx which is known to serve files in a very efficient manner, there isn't any reason why I'd choose to let this server do it.

This seems fantastic for a quick hack and a tiny mashup, but for anything bigger, I'd definitely give it a second look.

bad_user4• 16 years ago

> When I have something like nginx which is known to serve files in a very efficient manner, there isn't any reason why I'd choose to let this server do it.

For localhost development.

Manos de Mono: The Manifesto (.NET Web Framework)

Related Stories