4 ms·
Building an API with Go at Microco.sm
- redbad 13y agoNice overview. Somewhat frustrating to see non-gofmt'd code examples. Fix that up :)
- deleted 13y ago[deleted]
- motter 13y agoNone of the links work in the embedded version, but if you download the PDF they're fine.
- zeckalpha 13y ago18k lines? Does that seem high to anyone else? Or am I missing something important?
- realrocker 13y agoIt is high. Probably includes code site,docs etc.
- motter 13y agoHigh compared to what? It's just the output of wc -l `find microcosm/ -name *.go` so is really just a rough indication of the size of the project.
- zeckalpha 13y agoCompared to the amount of work that needs to be done for this project to function.
- motter 13y agoIn that case, I don't know a number that can be used for that comparison. 18k is the total number of lines in the source code files; the SLOC will be different. In hindsight, I should've left this number out. It was intended to give background to the overall program size, but it's a small detail that shouldn't be the focus of this discussion.
- realrocker 13y agoWell, Go has been touted for lower lines of code.
- ajack 13y agoAs a member of LFGSS and HN, yes!
- asselinpaul 13y agosame :)
- feniv 13y agoMy experience has been pretty similar: Go is perfect for building high performance APIs. A lot of the library infrastructure is still in early stages. One suggestion: Don't bog down your application server with serving static files (Slide 7. favicon and robots.txt). I put all of my css, js and image files in a /static sub-directory and configured nginx to serve any URL starting with /static without hitting my go-server.
- motter 13y agoThanks for pointing that out. The static routes in the talk are just for illustration -- we use nginx to serve them in production. One thing I haven't touched on at all is html template rendering, something I'd like to take a look at in detail at some point. Would like to hear more about your experience with Go -- is there a writeup somewhere?
- pjmlp 13y ago> My experience has been pretty similar: Go is perfect for building high performance APIs. Like any native compiled language, it is just a matter of having the right set of libraries available.
- Herbert2 13y agoDespite the overall ecosystem being rather small, the standard library and adjoining experimental packages are excellent. I wouldn't be surprised if go 1.2's stdlib would cover most of what Python's stdlib and Twisted can do.
- pjmlp 13y agoPlease call them web services or REST API, just API is confusing.
- koblas 13y agoMaybe I missed it - but it would be really cool to see a large fragment of working code for some of the apis.