Product Reviews - is there any value?

Product reviews have been commonplace in magazines, newspapers, on TV, etc. With the increased popularity of the Internet, everyone seems to write reviews on varying topics from products to movies. I've even written a review. With all these reviews out there, is there any value to them? That's, of course, a matter of opinion. Each reviewer has a bias, knows certain facts, has likes and dislikes, and maybe even an axe or two to grind. When I buy things, I typically read a lot of reviews that are all across the board; someone may not like a company because an employee was mean to them, or they could have had a bad experience with a piece of software (one that may only have happened on their machine), or on the other side, the reviewer may have met the author of a piece of software personally and felt a connection.

Years ago (about 10), one of my products was put head to head against a competing product. Both products were decent and the reviewer indicated the strengths and weaknesses of both. In the end, the reviewer said that they were evenly matched; however, the reviewer said this because a feature that my product had, the other product lacked, but the company that made the competing product promised it in a future update. This update never materialized and the reviewer, in my opinion, did a disservice to his readers by reviewing a promise and not what a customer could actually purchase and use. I'm still a bit bitter about this and makes me think even more about reviews I read. Reviews give me an idea of what other people think, but that really doesn't help me. I need to form my own opinions of a product.

Movie reviews are extremely common and I sometimes glance at them before seeing a movie. My wife and I like the same types of movies, usually action/mystery or comedy (she has a wider range of movie likes than me that includes romance), so we see action movies more than any other type of movie (we don't watch movies all that often). Before we went to see Firewall, I had looked at the reviews. It got pretty mediocre reviews at best. We both enjoyed the movie. It might not have all the things that Ebert and Roeper think make a great movie, but to us, it was worth the time and money to see the movie (TIP: Costco sells movie tickets for AMC Theatres; 2 for $15 which saves up to $2.50 per ticket).

In another case, I've seen reviews of products where the reviewer gave it bad marks because it didn't do exactly what he wanted it to do; the product never said it would do it, but that didn't matter.

Product reviews, from software to video cameras, to books to movies won't be going away anytime soon, but I'd hope that people form their own opinions and don't just make a buy/watch decision based on what someone else believes.

Holy crap!

I was sitting at my desk around 8:45 AM and heard a loud sound. I thought it was an earthquake, but the floor didn't shake. I checked the earthquake maps and didn't see anything. I then searched the house to see if someone was in the house, but luckily didn't find anyone. Then I spoke with my dad later and he said he heard the same thing; we concluded we heard it at the same time (he's about 30 minutes from me), so I poked around and found an article about it. Not sure if it really was a sonic boom, but it really scared me and the dog. I think it is the military; of course they'll never tell us anything.

Apple's Transition to Intel Revisited

I wrote awhile back on how moving an application from PowerPC to Intel isn't as easy as Steve Jobs has indicated. This topic has come up again and I'm a bit offended by what one author has said in a recent article where the author basically says that developers that have been using Xcode and have programmed in Cocoa have a relatively easy transition moving code. This may be true for simple applications, but doesn't reflect the reality of many applications out there. In one of the programs I've been working on for the last few years, we developed it using Xcode and used Cocoa throughout (OK, one slight component still has to be in Codewarrior as it needs to be CFM). One engineer spent several months making things work on Intel; the main reason is that the application talks to an external device over USB. Any application that talks to an external device is far more complicated than outsiders think. In addition, we have taken, what I consider an extraordinary step, in supporting third party plugins that weren't designed for Intel. Apple says that users should run applications that require third party plugins in Rosetta by forcing it in the Finder. I find that this is unacceptable to have to run a universal application under Rosetta just so that plugins can run as I want the speed of the universal application. So, additional work was required to get this to work seamlessly (I'm still amazed at how well this works) which most applications don't have to handle. (In this particular case, it is unlikely that most of the third party plugins we support will be made universal any time soon, so waiting for them to become universal is unrealistic.)

I got my first universal application running in about 5 minutes as the application has no external dependencies (no third party plugins or devices). A lot of applications fall into this category, but end users can't just say that developers don't care or aren't doing enough to move applications to Intel as users don't know the circumstances around application development. Even if a developer has followed Apple's lead to switch to Xcode and Cocoa, it doesn't mean they can put a universal application together in a few hours. As I'll be ordering a MacBook Pro in a few weeks, I'd love to see all my applications running as universal applications, but the reality is that the smaller applications and many shareware titles will be coming much sooner than the big titles such as Microsoft Word.

New Video Camera

Last week I went to use my Canon ZR85 video camera to record our dog doing something wacky. When I turned it on, instead of an image on the screen, I saw lines. After futzing around with it, I came to the conclusion that the CCD was busted as playback worked fine. We're going on vacation soon and I know that my wife will want video of it, so I started research into a new camera. I don't use the video camera all that much, so I didn't want anything real fancy and didn't want the bottom of the barrel. I went to Circuit City to look around, looked online, and settled on a Panasonic PV-GS36 that I bought at Costco for $279 (there was a coupon this week). For the price, I don't think I could beat it. It has similar specs to the Canon I'm replacing, but I must say that the user interface (via a joystick) is far superior to anything else I've seen. It seems to have everything I want and we'll see how well it does. I hate that we're a disposable society, but getting my Canon repaired would probably be a minimum of $100 to look at it and then the cost of parts. Then I'd only get a 30 or 90 day warranty on the repairs.