Re: [go-nuts] Re: Choosing a framework

2017-09-15 Thread Shawn Milochik
On Fri, Sep 15, 2017 at 7:50 AM, john howitt wrote: > One of my reasons for moving to Go was to escape from frameworks which in > my opinion are a fashion statement not a technology. Slightly mangling the > saying about Regular expressions "I have a problem learning Go", "OK

[go-nuts] Re: Choosing a framework

2017-09-15 Thread john howitt
One of my reasons for moving to Go was to escape from frameworks which in my opinion are a fashion statement not a technology. Slightly mangling the saying about Regular expressions "I have a problem learning Go", "OK use a framework", "Now i have two problems", "You can also use and ORM", "Ah

Re: [go-nuts] Re: Choosing a framework

2017-09-14 Thread Vikram Rawat
Thanks for the tip! But he is a newcomer and so am I. Tell us can we learn it. Is it documented anywhere. That's exactly what i told him. I would love to try vecty. But right now we can't figure out how to try it. 14-09-2017 9:14 pm को "Jim Ancona" ने लिखा: > On Thu, Sep

Re: [go-nuts] Re: Choosing a framework

2017-09-14 Thread Jim Ancona
On Thu, Sep 14, 2017 at 1:28 AM, Vikram Rawat wrote: > > And there is another project called VECTY. But I mailed them and they told > me it's not documented yet. and it could have bugs. > Vecty (https://github.com/gopherjs/vecty) uses Gopherjs and runs in the browser, so

[go-nuts] Re: Choosing a framework

2017-09-13 Thread Vikram Rawat
> > I am trying to learn golang too. and I have never ever build a website. > All the experience that I have is by building SHINY R dashboards.I tried > almost all the framework. But I liked REVEL. Because speed and concurrency > is not my concern I just want to write simple database web

Re: [go-nuts] Re: Choosing a framework

2017-09-13 Thread woosley. xu.
Personally when I started my project I chose to use a framework. I think it is ok to start with frameworks as long as you know what framework should do, what key concepts should be handled when dealing with Web app. Maybe Go provides all those solutions with standard pkgs, but if a framework can

[go-nuts] Re: Choosing a framework

2017-09-13 Thread Kevin Powick
Asked and answered many times in this group and in another popular Go forum: https://forum.golangbridge.org/search?q=framework Another collection of Go frameworks, tools, packages (libs) can be found in the following GitHub repo: https://github.com/avelino/awesome-go#web-frameworks There are

Re: [go-nuts] Re: Choosing a framework

2017-09-10 Thread Henrik Johansson
Maybe it is better nowadays but at least last time I tried a bigger framework the first thing that happened was I had to either change logger or wrestle with how the framework did it's logging. I would from experience in both Go and other languages (mostly Java, Spring is not your friend) very

Re: [go-nuts] Re: Choosing a framework

2017-09-10 Thread Henry
Actually, there is nothing in Go that prevents you from using any kind of frameworks. You are free to use whatever you wish. Go provides a more complete standard library for web development than many other programming languages. While in other languages you have to rely on frameworks, in Go,

Re: [go-nuts] Re: Choosing a framework

2017-09-10 Thread Tim Uckun
I will simply point out that go seems to be alone in this regard. All other languages that I know and have used have embraced the idea that it's OK to assemble various functionalities in a useful framework which one can deploy without too much effort. On Monday, September 11, 2017 at

[go-nuts] Re: Choosing a framework

2017-09-10 Thread Tim Uckun
On Monday, September 11, 2017 at 12:56:40 PM UTC+12, Florin Pățan wrote: > > Given your list of choices, I would go for Buffalo as it's probably the > closest you can get to an idiomatic Go code base while not having magic in > the code and still be able to understand what's happening when

[go-nuts] Re: Choosing a framework

2017-09-10 Thread Florin Pățan
Given your list of choices, I would go for Buffalo as it's probably the closest you can get to an idiomatic Go code base while not having magic in the code and still be able to understand what's happening when things go wrong. As others have recommended, also try writing your code without the