I don't listen to the radio hardly at all anymore. Recently, I was with my wife while she was just idly flipping through, and I was astounded.
The electro/techno stuff was autotuned, but that's less of a surprise.
Autotune, autotune, AUTOTUNE!
Not even subtly, either, but cranked up as far as it will go before the high end simply explodes with noise.
Is there anyone left in the music industry that can carry a tune?
I've pushed two repos to GitHub with Go code:
- gomempool (godoc): A byte pool manager for Go. It's less generic than the Pool implementation that is working its way into Go tip, but also therefore understands more about bytes, and is much simpler than the I-don't-even-know-what magic is in that implementation. It also tracks stats, which I've hooked up to my monitoring so I can see the usefulness of the pool in my real running code.
- abtime (godoc): An abstract time library that removes your dependency on the OS time from the time module. I've now run into this problem at work in three forms; unfortunately one of them is in a module I plan on releasing someday and don't want a dependency on this module, but the other two can benefit from a standardized way of dealing with this. I had a semi-complete version of this in my local code base already, but I was inspired to bring it up to public spec by Moonpig.
There's more coming, but they're bigger than these. My supervisor tree library is nearly ready to go, but the requisite blog post explaining the design is still in progress. (It's big.) The library that implements Erlang-style mailboxes, including the ability to cluster together machines and send messages across the cluster the way Erlang does, is still in progress. (I have just barely started the clustering.) My current plan is to lock down and stabilize the system this is being written for in the single-server case, then implement this clustering.
I wouldn't mention it, except that Google does not seem inclined to index these without some form of external link. GitHub permits external indexing of the master branch of projects but I think perhaps their robots.txt forbids the scraping necessary to find unlinked projects. Hopefully this fixes that.
Gold in vault, target
Steel door closed, locked, key thrown away;
Thief laughs "There's no wall!"
Data stream flows, filling
Lake overflows; disaster!
Man trusts fellow Man,
fellow Man undeserving.
Script code injected.
Output easy, just append strings!
Master needs new novice.
Dark secrets made, shared
Tells foe the password is lost...
Rubber hose finds it.
"Love", Alice tells Bob
In anger, Eve flips one bit
Now love's checksum fails
Small time differences,
like the blink of a blink, yet,
timing attacks still work.
Chick digs my profile,
sends regards in attachment.
Virus, still no love.
That plaintext password?
Easy, but when the press hears...
thought too hard to bear.
Address sign-up forms,
Security mindset sees
a way to spam foes.
One of my objections to Erlang is that despite paying the price of being a functional language, it often fails to reap the advantages. An example of this is in testability; nominally, a purely functional bit of code ought to be easier to test than the imperative equivalent, because it is just a matter of setting up your parameters and checking the results, with no IO or state in between.
Erlang doesn't make this impossible, but it's less convenient than the brochure promises. The core of your application is generally locked up in the various gen_* handlers. These handlers have very stereotyped ways of being called, which include the full state of the thing being tested. I find this very tedious to test, for two reasons: 1. Every test assertion must define some sort of "complete state" for the handler, which is probably full of real-world concerns in it. In particular if it has further messages it is going to send, those are often relatively hard-coded somehow... an inconvenient-to-mock Mnesia entry, an atom-registered process name, etc. (Erlang programs end up having a surprising amount of global state like that.) 2. If you want to test some sort of sequence of events, you are responsible for threading through the code, or manually invoking the proper gen_* start up functions, or something. It's possible to refactor your way out of this mess, but in practice it's a lot of work for the reward. So many of the tools you could use in other languages aren't available.
Go, in theory, ought to be harder to test than Erlang, being an imperative programming language. In practice, I'm finding it much easier, and I'm doing a lot more testing in it.
In response to this story about a possible impending Helium shortage, someone suggested on Hacker News that perhaps someday we can use nuclear fusion to produce helium.
As it happens I'd idly chatted with my wife about that a few weeks ago, but that wasn't enough motivation to run the numbers. This was. Could we produce enough helium to satisfy our commercial production of it through fusion, if we just assume we have fusion?
|<- Future Posts||Past Posts ->|