Tumblelog

This is one very good way to make sure that nobody ever manages to recover your data.

The funny thing here is that I could have been super-predictive because I wrote a science fiction story that died in rewrites about this very subject..... Oh well.

Using paper circuitry to make origami. How neat...

Hm. Going to have to try this with all my space Ethernet hardware...

I should play with some of these. I've come to love old games more than new ones.

So a guy I worked with once wrote something almost exactly like this. It was an excellent piece of software. I'm kinda glad that somebody else has gotten the same good idea.

This is something that I've given a lot of thought to...

Great robotics. The ultimate machine.

My rant: One can write all the GPL'd open-source whatever software that will do all kinds of rotten things to a Microsoft Windows Mobile 6 device that Microsoft doesn't intend for you to be able to do. But you can't do that with an iPhone.

I've always got a soft spot for the Apple IIgs. Somebody modded one into a laptop.

This looks interesting. I use SQLite in PhotoHub and there might be some neat tricks to be had there.

Makes a whole new way to construct a Ruby object that's simpler and more declarative. I've come to love languages where you can pull stunts like this...

I'm not entirely sure if this is a massive leg-pull or if this is something useful.

This is great. There's a continual chain of bottom-feeder-companies out there who specialize in selling an entry in a directory that everybody just tosses in the trash bin for $$$$$. Combine that with the desire to spend as little money on things that don't impress the clients and a desire to not have prospective clients be able to call up existing clients to find out how useless the service really is....

I love the Billboard Liberation Front.

Nice analysis. I wrote some code that intelligently called reserve() a long time ago but then ripped it out. Maybe I shouldn't have...

This is brilliant. I, however, have an even better idea. :D

I remember looking into client certificates somewhere around 1999. So, yeah, this is astonishingly right.

I remember working on a product that was rewritten to be partially in Java partially in C++ (because Java wasn't fast enough). By the end of it, I pointed out that they could have ported it once (from Unix to Windows) and it would have taken less time.

This is an example of how you can use logical arguments to say something really stupid. Just because you can imagine a program that runs for the expected lifespan of a computer yet doesn't fill up the address space doesn't mean that I can't imagine a program able to fill even a 64 bit address space within a very short amount of time.

I've seen this before many times. 99% of the time, your program probably can rely on a badly implemented reference count GC. But there's this one percent of the time where you need to pierce through all of the layers of abstraction and really grasp what's going on. This is why computer science programs that teach Java will always be inferior to programs that force students to program some level of assembler and C.