I am in the process of moving this blog over to Jekyll, while at the same time admitting that I’m never going to finish writing my own blogging software, and that I really should concentrate on the writing, and not the underlying software. This is also an admission that for a while there may be general brokenness such as broken links and some horribly formatted posts. Also, I will be turning on comments, which is a longer post in itself, but let’s just say that after years of watching abuse and generally uncivil behavior on all the social networks I’ve decided to revert to old technology from a simpler time, where I get to have absolute control over what appears next to my writing.

Why yes, the frogs in the pond across the road are rather loud. BTW, Google Science Journal is awesome.

The article Will Tech-Driven Deflation Export Japan’s Economic Woes to the World? reminded me of this video, "Evolution of the Desk": The origin for the above video is http://bestreviews.com/electronics#evolution-of-the-desk. Each time an object gets digitized that's one less object to manufacture, one less object to ship, one less object consuming raw materials. It's actually more surprising that this hasn't had an even larger impact on the U.S. economy. Update: A great slide deck from Hal Varian covers the same ground with a slightly different take, pointing out that much of this progress not only doesn't increase GDP, it actually reduces it, which is a problem of using GDP as a metric.

We just finished migrating all of our monitoring from InfluxDB to Prometheus and I thought I'd write up our reasons for the change. Please note that these are my own personal observations and relate to a specific project, these issue may not apply to you and you should evaluate each product for your own uses. Update: To clarify, the versions of InfluxDB and Prometheus that I am talking about are InfluxDB 1.

As we head into the fourth week of Pat McCrory's failure to conceeed in the NC gubernatorial race, it's important to look at McCrory's infantile behavior in a larger context. While it would be tempting to try to psychoanalyze his continued intransigence as yet another man-child temper tantrum, there are larger forces at work, of which McCrory is just one sad symptom. The root of the problem stems from the ever widening wealth gap and subsequent elite overproduction.

You might think that as the U.S. moves from an industrial and manufacturing based economy to a knowledge based economy that we surely have weathered similar tranistions. For example, as we moved from an agricultural economy to a manufacturing based one. While we did indeed weather the same changes, the vital difference is the timescale over which those changes took place. As you can see from this data on agricultural employment, we did experience a loss of 6 million agricultural jobs over a 50 year period from 1910 to 1960.

To get an idea of voter suppression in action let's overlap the The Racial Dot Map with Wake County's early voting locations.

Restart ESF Pauli % Low Entropy High Entropy Initial Conditions Entropy: Mean: Entities: Mean: Quanta Magazine published an interesting article in their Insights Puzzle column called Seeing Time Through a Liquid Crystal Display. Above is my version of the simulation, which operates on a basic level like the simulation presented in the article, but then adds in a few twists. At this point you should to read the arctile to understand the basic simulation.

Bitworking is now served over HTTPS thanks to Let's Encrypt, in particular to the rsc.io/letsencrypt Go library which made it trivial to implement. Next up, Webmention.

Building on The Republican race: Five degrees of climate denial, extended to the full seven stages: Stage 1: Denial Pre 2010 - The climate is not changing. Stage 2: Ignorance 2010 - The climate might be changing, or it might not, we just don't know. Stage 3: GAIA Bashing 2014 - Climate change is real, but it’s natural. Stage 4: We so tiny 2016 - Climate change is real, but humans aren't the primary cause.

What to do when it's late at night and your high schooler says his table wasn't able to complete their physics lab today because they were missing equipment, and the teacher said, maybe half jokingly, that they could complete the lab at home if they didn't finish it in class? That's right, you build experimental equipment in your garage. This is the Interial Balance we built from scratch using two hacksaw blades.

It's March 2016 and that means I've been building and maintaining httplib2 for over 10 years. As with most of my best software, httplib2 was initially a rage-based project, fed by my disgust on the state of HTTP client libraries in 2006. In the past 10 years it's gathered quite a following, with 0.9.2 current being downloaded from PyPI: 37297 downloads in the last day 210596 downloads in the last week 830573 downloads in the last month I'm done.

Update [June 2017]: Scratch that, after moving the blog over to Jekyll I moved over to using MathJax for LaTeX support. And I never did add Julia support, oh well. In the first of two enhancements to piccolo, LaTeX support has been added. Just put the LaTeX in a latex-pic element and it will be converted to a PNG, with the alt text set to the LaTeX code. <latex-pic>E = mc^2</latex-pic> Transforms into:

We do large displays for Halloween, usually involving converting the garage into a haunted house. They're major undertakings, with four or more actors, so we only do them every other year. I also try to roll a "build" into every Halloween. For example, 6 years ago I built this as part of the haunted house: And two years ago the same skeleton got taken out of the jail and laid out on a table, this time animated with pneumatics.

A sound effects board with the sounds of a dragon built using the Web Audio API. Because Halloween. Start Snoring Stop Snoring Sniff Roar Chains: [Source] Roar: [Source] Sniff: [Source] Snore: [Source] Code

Note: This post was updated in Jan 2017 to use the Custom Elements V1 spec. One of the questions that comes up regularly when talking about zero frameworks is how can you expect to stitch together an application without a framework? The short answer is "the same way you stitch together native elements," but I think it's interesting and instructional to look at those ways of stitching elements together individually.

Today Google launched gRPC, a new HTTP/2 and Protocol Buffer based system for building APIs. This is Google's third system for web APIs. The first system was Google Data, which was based on the Atom Publishing Protocol [RFC 5023]. It was an XML protocol over HTTP. The serving system for that grew, but started to hit scalability issues at around 50 APIs. The scaling issues weren't in the realm of serving QPS, but more in the management of that many APIs, such as rolling out new features across all APIs and all clients.

Subtitle if this were an academic paper, which it’s not: A k-means clustering derived point statistic highly correlated with regressions in commit-series data with applications to automatic anomaly detection in large sets of benchmark results. TL;DR: To detect regressions in benchmark data over a series of commits use k-means clustering on mean and variance normed commit-series. For each of the clusters find the best fitting step function to each cluster’s centroid.

Having recently moved to using Git from Mercurial here are my observations: Git just works No matter what I try to do, there's a short and simple git command that does it. Need to copy a single file from one branch to my current branch, need to roll back the last two commits and place their changes into the index, need to push or pull from a local branch to a remote and differently named branch, there are all ways to do those things.

Stop writing Javascript frameworks. Translations: Chinese Japanese Russian Here's the talk, based on this essay, that I gave at OSCON 2015. [Slides] The 100-line templating library presented as a Gist has been cleaned up, documented, and published as the Stamp library. JavaScript frameworks seem like death and taxes; inevitable and unavoidable. I'm sure that if I could be a fly on that wall every time someone started a new web project, the very first question they'd ask is, which JS framework are we using?