Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

Yes, I am, it's fast and great, but the UX in go is a bit annoying since you need to constantly keep checking for errors on literally every set (to check for possible area errors). So your code has even more `if err != nil {return nil, err}` than usual go code.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: