The 5mp Hero Wide now supports 4gb SDHC cards (the previous max was 2gb using standard SD). I haven't upgraded mine yet, but it looks like a simple firmware update that shouldn't take more than a few minutes. Their website says the same update will be available soon for the non-Wide (Standard) 5mp Hero Cam, too.

Full details here

An excellent article from The Economist: Driven to distraction

If you must talk, text or twitter, do not do it while driving.

2nd hard system crash in as many days. Snow Leopard system stability is pretty bad. I don't think I ever saw a full lock-up on Leopard 10.5, very infrequenet on Tiger 10.4.

On the plus side, full system crashes will probably distract me from the now-ruined Exposé.

Maybe I can downgrade back to 10.5? Ugh.

Interval Since Last Panic Report: 28807 sec Panics Since Last Report: 1 Anonymous UUID: 46FEE2D6-CFAB-XXXX-XXXX-XXXXXXXXXXXX

Thu Sep 10 14:32:18 2009
panic(cpu 0 caller 0x226297): "thread_invoke: preemption_level -1, possible cause: unlocking an unlocked mutex or spinlock"@/SourceCache/xnu/xnu-1456.1.25/osfmk/kern/sched_prim.c:1471
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x5b65be28 : 0x21acfa (0x5ce650 0x5b65be5c 0x223156 0x0)
0x5b65be78 : 0x226297 (0x5864e8 0xffffffff 0x586480 0x225b6c)
0x5b65bef8 : 0x22699d (0x6dfc01c 0x6dfc01c 0x5b65bf58 0x232085)
0x5b65bf68 : 0x226a08 (0x5474ba 0x6fb3940 0x0 0x84b720)
0x5b65bf88 : 0x547576 (0x5474ba 0x6fb3940 0x0 0x1c03)
0x5b65bfc8 : 0x29c68c (0x6fb3940 0x0 0x10 0x8fedca4)

BSD process name corresponding to current thread: kernel_task

Mac OS version:
10A432

Kernel version:
Darwin Kernel Version 10.0.0: Fri Jul 31 22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)

Briefly, here's my 2 cents after 24 hours on Snow Leopard:

• New Exposé is teh suck. Windows no longer retain their relative sizes in Exposé, which means a full-screen window might appear the same size as your tiny chat window. This is pretty dumb. I don't know how it was decided to ruin the solid, usable Exposé of 10.4/10.5 with this lame replacement, but this change makes the usage of Exposé non-intuitive, and that's a very un-Apple thing to do. Also, what's with the tacky blue-border? Did the Apple UI designers quit and get replaced by a pack of squirrels?

• Another big ding on new Exposé: the way it uses available screen space to render your windows is really, really bad. Try using it with a small-ish number of windows, maybe 3 or 4. Notice all the wasted, unused space?

• 10.6 feels faster than 10.5, but can't give too much credit here because 10.5 felt much slower than 10.4. And this is significant because every other transition (10.1 to .2; 10.2 to .3; 10.3 to .4) all felt faster. So Apple is back to it's previous reputation of increasing speed with next 10.x release.

• 10.6 install did seem to free up several gigs of disk space, although I didn't measure how much. Their claim of "7 gb" seems reasonable.

• They finally made it possible to hide the Finder sidebar (where the little shortcuts hang out). I hate that thing, and I think it was 10.4 when they forced everyone to have the sidebar, like it or not. Enough griping, it took them a few years but reason finally prevailed, now you can hide the Finder sidebar with Command-Option-S (repeat to show again).

Everyone should read this. Stunningly simple, it visually explains all parties involved in the healthcare discussion, and also what their motivations are.

Healthcare Napkins

Key point: insurance companies are a business, and for all their whining + complaining, we shouldn't forget that they ultimately have business interests at heart - everything else is secondary (quality of care, cost to patients, individual health improving, etc.).

All businesses exist to make money, and it's only natural that a business would oppose changes that reduce their profits/revenue. In the case of healthcare, any change will mean lower profits for the insurance companies, so they're generally against all change. They do recognize something has to change, but their preference would be to keep things as they are. Should individuals care? No.

Business climates change, and the public has no obligation whatsoever to preserve an old, dying business model just because the businesses who still operate in that old, dying business model are unwilling to change. Either you adapt, or you become obselete. Times change, get over it.

In general, consumers do a pretty good job of collectively figuring out which products are better than others. But for insurance, we don't have choices and we don't see the reality. A big reason why: the insurance companies themselves actively oppose choice and confuse everyone as an act of self-preservation. Why we even listen to them is beyond me, as they're arguably the most biased party in the whole equation...

It seems like all kinds of influential / significant people are dying these days.

Surely part of it is just perception based on my own age - the people I know about are reaching the end of their years. For example, when I look at the top music albums/tracks on iTunes, I don't recognize any of their names; so it follows that if any of them died, and I somehow heard about it, it wouldn't resonate with me at all.

But several people I do know about have reached the end of their days... John Hughes, Robert McNamara, Paul Newman, Ed McMahon, Michael Jackson.

If a great movie director died say 20 or 30 years ago, would you ever know about it? No question that we're better informed these days - thanks to websites / emails / etc. - so we find out about other folks' passing instead of them just passing by unnoticed.

Anyway, RIP John Hughes, thanks for the great films!

• Weird Science
• Ferris Bueller's Day Off
• Planes, Trains & Automobiles
• The Great Outdoors
• Uncle Buck
• Sixteen Candles
• Pretty In Pink
• Vacation + European Vacation + Christmas Vacation
• John Hughes complete filmography

June 9, 1916 to July 6, 2009
Robert McNamara

"The Little Engine That Could" is a children's story that delivers several lessons to the reader, some of which are obvious and others less so. I read it as a child and remember the obvious lesson of "think positive". Having read it repeatedly during recent weeks (by request of my son), I've come to understand and appreciate the less-obvious lessons, and I feel obligated to share these bits of wisdom with others.

Obvious Lessons

1. Think Positive - as long as you believe in yourself, you can accomplish great things. "I think I can, I think I can, I think I can." And then of course you do. It doesn't always work out like this in life, but there is truth to the power of positive thinking. This is the main lesson we get from The Little Blue Engine.
   
2. Don't Be Negative - if you can't think positive, at least don't be negative; by not believing in yourself, you will certainly not succeed. This lesson is a bit more hidden than the first. It comes from the old, tired engine who just doesn't believe in himself, so that's the reality he creates - he thinks he can't, he can't, he doesn't. What does being negative get you? Nothing, so don't do it.
   

Less Obvious Lessons

1. Maintain Your Vehicle - shown in the context of a train, but applies to cars, too. If you don't maintain your vehicle, it might break down and cause a ton of problems. Not just for you, but everyone else involved. And if it was preventable through regular maintenance, then whatever chaos ensues as a result of your broken-down vehicle is ultimately your fault. This comes from the very first engine in the story who was obviously not well-maintained, and breaks down as a result.
   
2. Don't Put All Your Eggs In One Basket - if you do and the basket breaks, you're shit outta luck. In the story, we are reminded of this lesson repeatedly - if the train doesn't make it over the mountain, then the kids won't have food or toys. Really? They've got nothing else to eat over there? And no toys? We're led to believe the children are sitting over there, presumably staring at the wall, hungry, bored, waiting for this train. (Sounds like most of Africa, but I don't see anyone writing cute children's stories about that.) Anyway, is the situation in the story really so dramatic? "Damn, if that train doesn't make it here by tomorrow, then the children are gonna starve! And be bored, too - no toys!" Whoever runs that town needs to wise up and get some more goods flowing in. And maybe inform the toy clown that he should tone it down a little because children in Ethiopia would love to have a train of food and toys show up late instead of not at all.
   
3. Just Because Someone Is In Charge, They Could Still Be A Clown - pretty self-explanatory. Leaders are often buffoons. In the story, the leader is a toy clown. In real life, many leaders (bosses, managers, directors, etc.) are often clowns, too.
   

What's up with film studios deliberately crippling DVDs?

While trying to create my own iPhone version of WALL-E, I've discovered that Disney crippled it with ARccOS. I own a fully-legal copy of the movie (3-disc set, no less), but due to ARccOS copy-protection b.s., I had to jump through several hoops to get the full-length movie onto my computer. I finally did it, and I hope others do it, too.

I'm not file-sharing or doing anything illegal, just want it on my iPhone. They do include a "digital copy" that will supposedly allow me to put the WALL-E movie on my computer, but it's just more copy-protected wankiness, has an access code, limitations, etc.

This really only serves to annoy paying customers, and does nothing to discourage thieves/pirates. I mean come on, all you need to know is which track to rip (30, in the case of WALL-E), and whether to time-shift the video (38 to 40 frames, possibly none at all depending on who you ask). Most 12-year-olds probably figured that out, and then the rest of the low-tech customers are just mad that they can't put the movie onto their kids computer. Nice going.

Someone pointed out in the forums that it's easier to download an illegal, pirated copy than it is to create your own backup copy from your own legal DVD. I think they're probably right. Wake up, Disney.

They did a study where they sometimes tricked dog owners into thinking the dog had done something they shouldn't do when the dog had in fact done nothing wrong. Basically the dog's expressions had nothing to do with anything, the owners behavior and conclusions of guilt/innocence are really the only factors.

Can dogs really look 'guilty'?

Researchers concluded that any such "guilty look" is a response to human behaviour and has no relation with the dog's actions or sense of having broken any rules.

I've heard about this several times, but never seen it. They say it's very inspirational. At a brief 15 minutes, I can't imagine it's not worth watching. Jobs is usually a captivating speaker, even when talking about mundane stuff.

While looking for an audio copy, I found a video version instead. Available on iTunes, and free.

Stijn Devolder took the Tour of Flanders for the 2nd year in a row. What a beast. I was rooting for Haussler (especially after he got nipped on the line in San Remo), but damn, gotta respect Devolder just storming away from the lead group on the Muur, 18km from the finish, and riding solo all the way to the finish. Nice ride!

http://www.youtube.com/watch?v=v9w5bhSnZE8

Click to enlarge

Here's a chart I made by extracting data from the overall results of the 2009 Capitol 10k. It shows the number of timed participants for each overall pace.

They sold 7,000 timed registrations (according to the initial registration form), of which 6,644 runners completed the event (according to the official results page). There were ~18,000 participants in total (according to news reports), so ~11,000 completed the event un-timed.

Anyway, for the timed runners, you can see pretty clearly how people did.

How can you do bulk file rename using shell tools?

The wrong answer is: mv *.OLD *.NEW

The easy answer is a shell loop, should be pretty straightforward. Or maybe even a simple Perl/Ruby/etc. script.

But it's also do-able using find with some other tools. Turns out that's rather awful. This is what I came up with to make it actually work using find, and as far as I can tell, it adds zero practical value over a basic shell loop. I spent a few minutes trying to use -exec, but that got hairy when using {} twice, and also when the output contained full paths from subdirectory traversals.

find . -name "*.OLD" | sed 's/^\(.*\).\(OLD\)/cp \1.\2 \1.NEW/' | awk '{system $0}'

Another option would be using xargs. If you wanted to rename all ".txt" as ".txt.OLD" (variation from above), that would be:

find . -name "*.txt" | xargs -I % cp % %.OLD

The example I initially gave is a little harder -- .OLD to .NEW -- you could use sed, too, in order to remove the file extension, like this:

find . -name "*.OLD" | sed 's/^\(.*\).OLD/\1/' | xargs -I % cp %.OLD %.NEW

Or you could use basename instead of sed, and call xargs twice, like this:

find . -name "*.OLD" | xargs basename -s .OLD | xargs -I % cp %.OLD %.NEW

This is a nice interview question for someone with Unix chops, because it can (should?) lead to a short discussion of shell tools.

The new MacBook Pro is a step backward from the previous version.

I used a brand new 15" MacBook Pro (backlit LED display, glossy screen, black border, extruded keyboard, etc.) for more than 3 weeks while my previous MacBook Pro was being fixed (it was hit by NVidia graphics failure). My old MacBook Pro finally came back, I've migrated my work back to it, and I'm happy to switch back.

Overall, I'm suprised at some of the changes Apple has made, a few of them are particularly bad.

Glossy Screen

This one just makes no sense to me. I don't know what MacBook (non-Pro) users thought of the "glossy-only" option, but everyone I know who uses a MacBook Pro for work complains about this. And they're right - the power of a laptop is that you can take it with you, and 3 weeks has told me I had no idea how much variance there is in lighting during the day.

But thanks to the new glossy screen, I was painfully aware of windows, lamps, overhead lights, anything flashing, anything moving within 50 feet.... This may be my single biggest beef with the 15".

Why did they do it? Apple knows the glossy screen blows, which is why they offer a $50 upgrade on the 17" model. But no upgrade on the 15"!

New Trackpad

This one is pretty bad, a close 2nd behind the glossy screen. I'm not the only person who noticed that the trackpad button makes my fingers tired. I found myself trying to avoid using the mouse altogether. Note that I use an external mouse/keyboard most of the time, so for me to rate this as a big complaint is significant.

When they increased the trackpad size (to accomodate frivolous mouse gestures... seriously, they're just fluff) they also increased the trackpad so much that you'll find other parts of your hand accidentally touching the trackpad surface, which creates screwy mouse input.

The mouse software ain't all there... maybe they've fixed it in recent updates, but I couldn't get double-click-and-hold to work, nor could I reliably double-click-and-drag to select text. Just forget it. I asked another saavy Mac user to try on the new MacBook Pro, and he couldn't do it either. I ended up disabling all of the fancy mouse features (including basic double-click stuff that the old MBP - and every other Mac laptop for the last 8 years - did just fine). Lame.

New Keyboard

This may just be personal preference, but I like the old / traditional style keyboard better. I heard the justification is that keycaps pop off more easily on the previous scissor-style keys, so these new rectangle button things don't come back for repairs as much. I don't know. I type a lot, and I type fast on the old keyboard, but on the new one I type slow. Why should I get used to it? It was a good keyboard before.

New DVI Port

You cannot use a DVI display without spending $20-30 on a special mini-DVI-to-DVI connector. Grr. And if you want to use a projector, you have to buy a 2nd connector, this time mini-DVI-to-VGA. And no, you cannot use a DVI-to-VGA adapter with the first connector you already bought, because the interlace pins don't line up. And if you chop them out, it won't work (I know a guy who tried).

There's ~$50 in crap just so you can use your brand new computer the way you used to. My previous MacBook Pro (and PowerBooks before that) included these connectors for free.

Firewire 800 Only - No Firewire 400

This is just a plain nuisance. We have lots of Macs around the office, and I have Macs at the house. Everyone and their dog uses FW 400 cables, but when it came time to migrate my data from old to new MBP, I had to... go to the freaking Apple Store and spend $40 on a Firewire 800 cable.

This cable + mini-DVI connectors + tax is ~$100 in crap.

No Front Row Remote

Admittedly, I haven't used this much, but it used to come free with your computer, and now you have to pay extra. They've already got you buying display adapters and Firewire 800 cables, why not add to the fun and pay extra for a remote, too?

Screen Hinge Moves Too Easily

This must have been a complaint point from weak, lazy users, I can't think of anything else that would justify the insanely friction-less ease with which you can now close the laptop screen. It's a laptop people, so when you move the computer it would be really nice if the lid didn't glide shut in the process. And no, I'm not exaggerating. Several times I had my work interrupted, connections closed, etc. because the lid slid shut on its own.

Removed "Enter" key, now "Option" key

I don't understand this. "Enter" and "Return" behave differently, and for years Apple laptops have included both. Now, for some reason, they decided they needed a 2nd "Option" key. Why?

Speed Feels The Same

This is just subjective, but most of the time, a laptop upgrade includes a snappier, faster feeling. But this didn't. I went from the non-glossy 2.4 ghz MacBook Pro to glossy 2.53 ghz MacBook Pro (4gb ram in each), and it felt... just about the same. I did some benchmarks, and the numbers were a little higher on the 2.53 in a few areas, actually lower in others. Why doesn't the new "faster" MacBook Pro actually feel faster?

Silly Shortcut Keys

They re-did the shortcut keys from previous laptops, so in addition to default keys for Dashboard and Exposé (I'm ok with these, OS-wide features that are practical for all users), they added keys for iTunes which just reeks of dumb Microsoft "multimedia keyboard". Come on Apple, this is a $2,500 computer.

Can we please avoid keyboard buttons that appeal to 8-year-olds? Or maybe just go with it and add "Post New Tweet" and "Update Facebook Status" buttons? I bet the kids would like those, too.

I just read an interesting question & answer at www.cyclingnews.com - "Eating on the bike". I don't know that I've seen anything definitive about caloric absorption rates (during exercise or otherwise) so the response from Scott Saifer is pretty interesting:

"... typical [caloric] absorption rates quoted are in the vicinity of 150 calories per hour for small, un-fit people, up to 325 or so for large, fit, genetically endowed people on good days ..."

The original question was posed because energy food manufacturers have suggested/recommended serving information that would have you consume 900+ calories per hour, which makes no sense whatsoever, except for the company that stands to make more cash by selling you more energy food.

I've been digging into some odd behavior that ultimately traced back to periodic changes to Windows system clock. After doing some research, I've found that:

• Sun's JVM (through 1.6) has a bug that pushes the system clock into the future faster than real-time.
• I've observed clock drift by as much as 3 minutes in 1 hour
• there's no single trigger that your code can do (or avoid), it seems many people have observed the clock drift in different scenarios
• the bug is still open in Sun's bug database: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6435126
• as of June 2006, they're targetting Java 7 for a fix, and as of March 2009 the bug is still open
• this affects Windows only, and the underlying cause is ultimately something screwy with clocks and timers on Windows

The Sun-recommended workaround -- as documented here http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6435126 -- is to create a zombie thread at JVM startup. This has the effect of fixing the clock drift issue on Windows, not sure if this needs to be excluded/ignored if you have a multi-platform product, but it should be pretty straightforward to do an OS check and ignore if OS != Windows.

new Thread() {
	{ this.setDaemon(true); this.start(); }
	public void run() {
		while (true) {
			try {
				Thread.sleep(Integer.MAX_VALUE);
			} catch (InterruptedException ex) {
			}
		}
	}
};

Download here: http://www.omnigroup.com/applications/omnidazzle/

I've been using OmniDazzle since it was in beta, bought a license as soon as it was available. It's hands-down one of the most useful apps I've ever used, especially in the workplace.

As of Wed Feb 25, 2009, OmniDazzle is now totally free.

I'm not sure why they changed the license. When I bought it, I paid $15, and I assume they were still charging the same until recently. I guess by making it free, they don't have to focus as much on fixes/tweaks/updates, although the app seems to be pretty stable... since purchasing 1.0 in June 2006, they've only released a handful of minor updates, even now they're only at version 1.1.

Anyway, all Mac users should grab this utility now. It's both useful and silly, and at $0 the price is just right.

While doing some performance testing for a Tomcat-served webapp, I discovered you can enable automatic gzip compression based on content-type. In basic testing, this resulted in ~65% decrease in data transmitted from server to client. Considering a page with 400k of content, that could shrink down to 100 or 150k total. Good stuff.

A great tool for performance benchmarking is YSlow (http://developer.yahoo.com/yslow/), which hooks nicely into Firebug. Using YSlow I was able to see as much as 80% reduction in transmitted data after enabling Gzip.

Note that Tomcat will not compress content unless the browser identifies itself as understanding Gzip compression, which it does on each inbound request.

Here are the steps to enable Gzip in Tomcat:

1. edit conf/server.xml
2. find the Connector, should look something like this: <Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" minSpareThreads="25" port="8080" redirectPort="8443" maxPostSize="0" />
3. add the following: compression="on" compressionMinSize="512" compressableMimeType="text/html,text/xml,text/plain"
4. based on Connector definition from above, mine looks like this after making the change: <Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" minSpareThreads="25" port="8080" redirectPort="8443" maxPostSize="0" compression="on" compressionMinSize="512" compressableMimeType="text/html,text/xml,text/plain" />
5. restart Tomcat

Reference documentation for v5.5 here:
http://tomcat.apache.org/tomcat-5.5-doc/config/http.html

iTunes Doodad won an award today. It has been certified as "Excellent" by FindMySoft.com. They made me a custom graphic, too.

I can hear it already... some of you are you saying, "So what? That graphic was probably auto-generated by robot software". But hey, how many auto-generated robot graphics have been sent to YOU on behalf of a website you've never heard of? Mmm hmmm, that's what I thought.

But you know what, don't focus on the negative, man. If you are true to yourself, with a lot of hard work, you too can follow your dreams and have a robot stranger send you a graphic that you can post on your website. And that'll just be the beginning.

Ok yeah, I'm done. It's neato though, their website seems legit, has Google PR 5/10 so it's not some fly-by-night scam. But it doesn't take over my personal favorite "included in Japanese Mac magazine" success. They sent me 2 copies after they published it, couldn't read a damn thing.