3 ms·
I've just finished building an API in Go, and my experience was: You have to write more actual code than in Rails (or even ASP MVC), so it takes longer to deve
by marcus_holmes 13y ago
I've just finished building an API in Go, and my experience was:
You have to write more actual code than in Rails (or even ASP MVC), so it takes longer to develop, but it's much more satisfying.
I'm not 'web-scale' so the speed differences didn't actually matter that much. I didn't optimise for speed and the benchmarks were still impressively exceeding our requirements.
The standard library is amazing in places, but there are some libraries (gorilla in particular) that are almost obligatory.
If you have to write 2 API's you'll re-use a lot of code... you've effectively rolled your own API framework.
If your editor can handle snippets, make one for "if err != nil{" since that's a good 25% of any go program it seems ;)
Go is deep; the tools are deceptively simple and amazingly powerful. I refactored a lot as I went along and discovered better, more elegant ways to do things I'd brute-forced on the first iteration.
It was fun! Go is a really lovely language to code in.