Re: [go-nuts] Choosing a framework

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

Re: [go-nuts] Re: error handling needs syntactical sugar

| However, what's great for avoiding straightforward failures becomes a | nightmare when your goal is to guarantee that no undefined behaviour | happens It seems to me that if this is your goal other languages are more suitable. Erlang for example is famous for it's error handling capability, elm

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

2:18:54 PM UTC+12, Shawn Milochik wrote: > > On Sun, Sep 10, 2017 at 10:05 PM, Tim Uckun > wrote: > >> >> I understand the sentiment but I am really confused by this advice. Are >> you saying I should write everything myself? My own CSRF implementation, my >&g

[go-nuts] Re: Help with viper please.

hope this helps. > > On Sunday, September 10, 2017 at 2:05:40 AM UTC+2, Tim Uckun wrote: >> >> I have this code >> >> v := viper.New() >> v.SetConfigFile("settings.yaml") >> v.AddConfigPath(".") >> v.AddConfigPath

[go-nuts] Re: Choosing a framework

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 thin

Re: [go-nuts] Choosing a framework

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

[go-nuts] Re: Do you guys use ORMs when working with SQL?

Wow. the amazing amount of projects mentioned in this thread are interesting. Surprised that by now there isn't a well established leader or leaders for such a common need. On Sunday, September 10, 2017 at 10:01:51 AM UTC+12, Denis Isaev wrote: > > Take a look at kallax

[go-nuts] Help with viper please.

I have this code v := viper.New() v.SetConfigFile("settings.yaml") v.AddConfigPath(".") v.AddConfigPath("./settings") v.AddConfigPath("./config") err := v.ReadInConfig() if err != nil { panic(fmt.Errorf("Error when reading config: %v\n", err)) } if as the instructions say I don't

[go-nuts] Choosing a framework

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

Re: [go-nuts] Re: error handling needs syntactical sugar

>I *like* the way go does error passing, *because* it's constrained to handle errors explicitly. But it doesn't though. You can completely ignore the errors if you want. > >TBH, no. Not only do I not know what this is supposed to be doing (err.pop? of what? Why are we assigning to error? What is

[go-nuts] Re: error handling needs syntactical sugar

Totally not a go programmer but here are my worthless two cents. I don't see anything wrong with the try catch paradigm, you can choose your granularity. If you want to check every call then you can, if you want to let a few cluster together you can. You guys make is sound like go style error