はてなブックマーク

“Those who don’t know history are doomed to repeat it.” ― Edmund Burke There are many variations on this saying but the essential element is that it’s important, and I would argue useful, to know the history of something. It can provide depth, understanding, and insight. At the moment there are many debates going on about package management in Go. There are questions being asked, such as how shoul

Out of the box, Go provides just enough package management to make for a fast and efficient compiler. While it’s not opinionated enough to drive anyone away, Go package management doesn’t have the features to meet the needs of many developers. Especially for developers coming from PHP, Ruby, and node.js. To add features, a number of developers have built package managers that sit on top of the cor

Since I began talking about the Go programming language I’ve been asked why I like it so much. This post is a response to those questions. For those of you who don’t know, Go is a fairly new compiled programming language designed for concurrency and modern hardware architectures. At the core of all of the reasons for liking Go is that it is an engineered language. Some programming languages I’ve u

When I was working on a script to preload images with JavaScript one of the decisions I had to make was whether to use document.createElement('img') or an image object to preload the image into. The recommended w3c method is to use document.createElement('img') as it is a consistent way to create elements. This is the method I used. But, I was wondering which performed better. So, I ran some tests

Creating effects on websites using jQuery and other JavaScript has really grown from flashy extras to full on applications in the browser. Part of slick applications is images. They might be part of the content being loaded or something like an icon in an application. But, for those images being added after the page is loaded there can be a time gap while that image is downloaded. To avoid those t