As another commenter mentioned, I learned about Martini midway through writing this.

I really like Martini - if it existed a bit earlier, I probably would have just used it and been happy.

That being said, there are some differences between the packages. First, Martini has great plugin support because 3rd parties can inject their arbitrary type into handlers. On the other hand, gocraft/web has nested routers and middleware, which are really important for my own projects.

This may be temporary, but gocraft/web also has faster performance because it does less reflection, and because it's router is O(log(N)) instead of O(N). (See https://github.com/cypriss/golang-mux-benchmark , especially as you add more routes).

Finally, I prefer a more consistent signature to my handlers. Martini optimizes for flexibility. And depending on how much you want to inject into your handlers, your argument list can get really long.

Overall, I think Martini is absolutely great and think it's one of the best Go web libs out there.

Martini is relatively new, so there's a good chance it was released after he started work on this.

I'm new to this syntax too, but I believe it's just a reference to the function `SayHello` as defined on the `Context*` type. That is, if you have:

    func FuncA() { } // normal function
    func (int) FuncB() { } // function on an int object

You could later reference those functions via:

   var func1 := FuncA // assign FuncA into func1 var
   var func2 := (int).FuncB // assign FuncB into func2 var

But again, I'm just piecing that together from context and haven't looked at the spec.

This is calling the method assigned to a Context, which would be defined as func (c *Context) Something(whatever) {} If you have a w Context variable, you could do w.SayHello, with this you just call the function without an intervening variable, straight from the definition

> but have recently seen some mvc apps where models/views/controllers are grouped together by function/name

Can you put links to some of those apps that use that approach?

While using gocraft/web I've slowly come to the realization that it would be very convenient if the Context already knew about the Request and Response (without me having to pass web.ResponseWriter everywhere).