Tuesday, April 19, 2005

Still too wide: Samsung HL-R4266W

Samsung HL-R4266W Intro - Samsung HL-R4266W review - Projection TVs - CNET Reviews

The Samsung HL-R4266W gave me high hopes. I am looking for a set that will nestle into my 38.5" wide entertainment center. I would love to get a DLP at some point, but it's difficult to find sets that actually fit into this entertainment unit and are as large as possible.

This unit will be quite affordable when I will be be able to enter the TV market (10-12 months). But alas, it's width is 39.3". Quite starling when you consider the HL-R4677W is 40.6" wide. Perhaps Samsung's site is incorrect and the 46 is wider...or, hopefully, vice versa. The ratios don't seem to add up. I would expect the 42" to be 38" wide or the 46" to be 42" wide. Something just isn't right.

The ironic thing is, Samsung had the HL-R4266W on their site a couple of weeks ago, but it has since dissapeared. I'm really hoping the dimensions for it are incorrect.

Monday, April 18, 2005

Time editors asleep at the wheel.

Ann Coulter Cover Story Photo

Someone isn't quite there at Time. This caption is just flat out wrong. They don't even understand that all of the signs there are parodies by right wing group Protest Warrior.

I mean maybe they can't read, "Criminals for Gun Control". But CommunistsForKerry.com should have tipped them off.

Wednesday, April 13, 2005



I've been playing with some new Unit Testing technology called TestNG. If you've used JUnit or any of the XUnit clones, you probably understand the power that those tools provide.

But as I've found, JUnit is great for testing classes...but what happens when you're trying to do tests on dynamic input? What happens when you're trying to see if the input stream is valid based upon different contractual based rules?

That's where TestNG can be quite handy. I've tried writing these tests in JUnit and end up being quite thankful the tool is open source. Why? Because I end up hacking the JUnit code to death in order to make it dance.

Essentally in order to write my varied input stream test, I had to override many of the JUnit methods. In TestNG, I override none. I author a Factory annotated method to create instances of TestClasses, and TestNG will run each instance. In JUnit, I parameterization is quite difficult, requiring several add-ons. TestNG has this functionality built right in.

TestNG is young. It's still changing, but the development team is very receptive. I had an issue with execution order annotations (@beforeTestMethod for example), where they did not execute as expected when passed in through a @Factory. Within a few days of understanding the issue, it was resolved with a patch.

I highly reccomend checking TestNG out if JUnit has ever frustrated you when you want to do more than just unit test. Systems Integrators and product implementations groups would definately see the benefit from this tool as they are much more likely to have to run more flexible tests.

Friday, April 01, 2005

OpinionJournal - Cross Country

OpinionJournal - Cross Country

If you're in a technology job or field, like I am, you may find this political analysis of Silicon Valley quite interesting. Apparently, everyone there is a Libretarian (As time goes on, I think I'm taking on more Libretarian ideals)