I rewrote my blog in Go
ironzebra.com
I rewrote my blog in Go
1–10 of 77 posts
Re: I rewrote my blog in Go
#2"I removed the Disqus comments"
Wouldn't that by itself be enough to account for the download time differences?
Re: I rewrote my blog in Go
#3"I removed the Disqus comments" Wouldn't that by itself be enough to account for the download time differences?
Yes:
"I removed the Disqus comments and the many many lines of CSS from the old site and replaced it with only a couple of lines of CSS alongside a CDN-hosted copy of Twitter Bootstrap. Finally, the Go site is deployed to a free instance of Heroku and the MongoDB hosted on a developer version of Mongolab, while the old Django site was hosted on a Webfaction shared server. All these things influence the validity of a direct speed comparison between the two versions"
Indeed, all these things _invalidate_ the direct speed comparison between the two versions.
Re: I rewrote my blog in Go
#4"I removed the Disqus comments" Wouldn't that by itself be enough to account for the download time differences?
Sure would be. I would expect that to have quite significantly more effect than any of the other changes, probably more than all the other changes put together.
Re: I rewrote my blog in Go
#5"I removed the Disqus comments" Wouldn't that by itself be enough to account for the download time differences?
doesn't disqus start replacing a specific div on a page ready event?
If so, disqus loading is 'postponed' to after page loading? Or is it taken into account?
Re: I rewrote my blog in Go
#6How did you achieve a 16 second response time for your blog? What the heck were you doing?
Re: I rewrote my blog in Go
#7|and I decided to give it a go.
Never gets old.
Re: I rewrote my blog in Go
#8While rewriting things in different language is fun (and fun is a great reason to do stuff), the speed of delivering what is ostensibly static content is a solved problem. This was completely unnecessary. Bake the blog post into static HTML and tune up Nginx to shove it down the wires as fast as possible. Stick it on an CDN somewhere if it's important. Then move on to a problem that doesn't already have an optimal solution, and share the solution if you're nice. That's how everything should be done.
Re: I rewrote my blog in Go
#9I'm not sure why you wouldn't cache anything. It doesn't matter if x is faster than y. If both were cached the difference might be milliseconds and in the real world that is what will happen.
Re: I rewrote my blog in Go
#10It seems that people on hn just fell in love with go. So many new articles lately. It's like the node.js fever all over again.