At this point haven't you just built your own framework? You looked around,
did some research, read a whole of documentation and decided that this set
of components work well together and do what you want.
It seems to me that a framework is the exact same thing except that
somebody else has c
Here is a list of useful components that I sometimes reach for when I
need to do something in HTTP land that requires that I leave the comfort
and safety of the standard library but don't want to get locked into a
"framework". There may be better implementations of some of these, but
the ones liste
This topic has been discussed many times on this list. Do a search and
you'll see a lot of great points.
My opinion is that you should use the standard library, and only reach for
individual components when it would provide a significant advantage. Do not
use any "framework." Like Go's object-orie
Do you have experience with this? Can you say a couple of words about it?
On Sun, Sep 10, 2017 at 11:53 AM, Rodolfo wrote:
> https://echo.labstack.com/
>
> 2017-09-09 19:51 GMT-04:00 Tim Uckun :
>
>> I am in the process of learning go and decided to do it by writing a
>> (mostly) API based web s
https://echo.labstack.com/
2017-09-09 19:51 GMT-04:00 Tim Uckun :
> I am in the process of learning go and decided to do it by writing a
> (mostly) API based web site. I have been doing some research and have found
> the following.
>
> Revel: https://revel.github.io/
> GoBuffalo: https://gobuffal
I am in the process of learning go and decided to do it by writing a
(mostly) API based web site. I have been doing some research and have found
the following.
Revel: https://revel.github.io/
GoBuffalo: https://gobuffalo.io/
Iris: https://iris-go.com/
In addition there are "toolkits" like chi a
