Like many of you, I was pretty excited after T-Mobile made the Android 4.4.2 update (KitKat) available to the HTC One. After installing it, things seemed OK at first, and I was pleased with the new Sense tweaks.....Then my battery started to die. Rapido.

 
 
DISCLAIMER: This isn't a "bash redis" post. We use redis as a non-persistent key/value store here at Weebly and are happy with how it performs in that function. I'm thankful for all of the work Salvatore and the community have done into making redis a great key/value store. This post solely addresses using redis as a LRU cache replacement for memcached.

Ever since Danga Interactive's/LiveJournal's memcached burst on to the Internet scene, it has become the de facto general purpose caching application for people running larger scale Internet sites (or anyone just wanting to cache expensive operations). And why not? It's a pretty good program that's well written and has extensive library support. The major drawbacks to memcached are its slab allocator memory model and maximum object size at startup. Let's take a look at those.

 
 
In the past few years, we've seen a lot of new payment technologies deployed in the US. Just to name a few, there's Square, Google Wallet, Square Wallet, Bitcoin, Coin, Wallaby, and ISIS (the last 3 only being launched this week). Some of these are pretty worthwhile. Some of these are pretty terrible. Here's a quick rundown of what each is.

 
 
I swapped out my T-Mobile SIM card yesterday for one of their new Advanced Security SIMs, and WiFi calling suddenly stopped working. I poked around the Internet and found a lot of posts about REG09 and REG99, but not much on REG90 except one misinformed post where someone said that they had to return their phone.