Hacker News new | ask | show | jobs
by codegangsta 4581 days ago
If you don't want it then you don't want it. Both Gadget and Martini pretty clearly outline the value that they bring to the table. If that value proposition does not win you over then these frameworks are not for you.

I personally have seen a great improvement in code simplicity, readability, and overall DRYness when projects are written using Martini.

Choosing a framework isn't about following some sort of socially acceptable way to build your web apps. Just build them! If a framework solves a problem for you then use it, otherwise keep using net/http handlers.

1 comments

I'm glad you like these frameworks, and I not telling anyone not to use them. Like I said, I was just interested in hearing why I would want something like these frameworks which focus on server side templating, over a HTML/JS frontend + webservice approach. If you are just writing a webservice I think using Gorilla in addition to net/http is pretty much perfect.
shameless plug. Martini doesn't even have html template rendering out of the box. I originally built it because I wanted a better experience building webservices for Angular frontends :)

https://github.com/codegangsta/martini

You and I sir, are on the same wavelength

Interesting, I'll have to play with it. Thanks for sharing.

You should consider adding benchmarks to that it is easy to compare martini to net/http. This will let you keep an eye on performance as you work on it and accept pulls.