It's been a few months since I last spoke about
hyper. The reason I've been so quiet is primarily
because not much progress has been made on the project. I've been swamped with
other projects (most notably Project Calico),
and that's limited my ability to make much forward progress.
Right now the CPython core development team are having an extremely lengthy
whether to enable certificate verification for HTTPS clients.
When it comes to making this the new default behaviour in Python 3.5 the
response is an enthusiastic "Yes!" (just as it should be). However, when it
comes to backporting that behaviour to a patch release of Python 2.7 the
response from the core committers is distinctly more lukewarm.
About half an hour ago I pushed the latest release of
hyper, v0.1.0. This marks the
first release of hyper since early March! This delay is not because I've been
resting on my laurels. In fact, a quick check of the
git repository shows
that there were almost as many commits between v0.0.4 and v0.1.0 as there were
in total up to v0.0.4.
There once was a time when we were in control of our identity. When we met
someone we were in control of who we were to them. We could present ourselves
as whatever version of ourself we chose: the intellectual, the party animal,
the sports fan. We could withhold information, and the balance of probabilities
was that the information we withheld would be left undiscovered.
Logging is an interesting subject. For most developers, most of the time, we
don't think too hard about logging. Maybe we've got some coding standards that
mandate some minimal level of logging, but otherwise we're just not concerned
about how we log. But one day you'll find yourself five hours into a marathon
debugging session, throwing
print statements in random places and thinking to
yourself "If only I'd put in some logging here, I'd have some idea of what was
going on in this system!"