python -m SimpleHTTPServer
Anyway, kudos for making a Go project shipped, which I fail to accomplish for several months now ;-)
I was helping run a programming workshop last week and I wrote my own tiny concurrent server in Go but in the future I think I'll just use Caddy (https://github.com/mholt/caddy).
python -m http.serverWhich is not usually relevant if you just want to share a file over local HTTP. If you need a production-level HTTP server, you're not using either.
> it's certainly faster to type "ran" than "python -m SimpleHTTPServer".
If you're smart enough to compile ran and put it on your PATH, you're probably smart enough to create an alias for `python -m SimpleHTTPServer`.
It is faster to use an existing tool (python or another one) than rewriting a 2K LOC one. This is great for learning Go but the compounded time "lost" with a "slow" python server is nothing compared to the time this tool will require in development, debugging and maintenance over the years. As anyone else, I am subject to NIH and I can understand why writing one's own library is interesting by itself. Please don't invent weak excuses like "ran is faster to type".