HOME

August 17, 2010

Why I Don’t Have an iPhone 4

I call this: phones,tech — Posted by KP @ 12:53 am

I have blogged a bit about my decision not to purchase an iPhone 4 when it came out. First here, and then here when antennagate happened, and a little bit here. It’s now been nearly two months, and I still haven’t got one.

The first reason is that I’m totally, completely broke.

But the real reason that I’m not simply a few hundred dollars more in debt than I already am, and the owner of an iPhone 4, is that I’ve never seen one. It didn’t dawn on me until this week. In my money-saving mode, I’ve spent the entire summer without going to a mall or electronics store, and especially not the Apple Store. I’ve never seen an iPhone 4 in person, or held it in my hands. And I do believe that’s why I haven’t been bothered by the fact that I don’t have one (except when taking photos and wishing I had a better camera and/or a flash).

So I think this is a good thing, but it makes me wonder if I should accidentally come into contact with one, if suddenly I’ll involuntarily waste a bunch of money. Probably.

I’m going to try to put that off as long as I can, mostly because I’m still convinced that it’s an inferior product and I should save my money and contract commitment for something better. And it’s a day ending in “Y” so there’s another new rumor this morning about the Verizon iPhone, specifically that code for it is included in the latest OS — apparently the source who leaked this info says that the unreleased model in question is a CDMA phone, but so far as I can tell in my not-a-phone-engineer expertise, there isn’t actually anything in the code that indicates what kind of radio it has. There are also steady reports of a new iPhone (which everyone seems to be assuming is Verizon’s) in January.

At this point, I’m beginning to take a personal stake in the Verizon rumors, because now I’m depriving myself of newer technology, hoping that in the end I benefit somehow from waiting. If the next iPhone to come out is on Verizon, that will have been a worthwhile wait.


August 16, 2010

Stop Using Your New Macbook Pro Adapter

I call this: mac,tech — Posted by KP @ 8:37 pm

In my travels across the internet, I had a brief virtual conversation with an unfortunate person:

This person had a newfangled Macbook power adapter, like the one that came with my laptop, as this illustration from this post indicates:

Now think about this: what is the purpose of the Magsafe adapter? It’s so that when somebody trips over your power cord, the connector pops off harmlessly, rather than your laptop being dragged off the table, or the connector being bent or damaged.

But look at how the new one works: if someone trips over your cord to the left, the cord pops off. If they trip over the cord to the right, the wire bends around the side of the laptop and drags it. You can try this yourself by gently pulling in either direction, and you will see that you can make the laptop move and spin by pulling to the right.

This might just be a theoretical problem, but the poster also provided a gruesome photo of a huge dent in the corner of their MacBook Pro created by what would have been a complete non-issue with the old style adapter. That’s it. The moment I get home, I am swapping this adapter with the one that stays attached to my desk, and my laptop is never going out in the world with one of these new adapters again.

This is worse than antennagate when it comes to fixing something that wasn’t broke in the attempt to make it look cutting edge, while removing its sole function. If you have an old one, you might want to go back to using it in situations where somebody might trip on your cord. And if you don’t and you really love your Macbook, you might want to find an old one someplace, because Apple’s stopped making them.


August 15, 2010

The J/K Tree

I call this: summer stock,theatre — Posted by KP @ 8:18 pm

Gather ’round, children, and I will tell you the story of the J/K Tree.

(For anybody over the age of 20, or people who spend too much time in real life, and not enough time on the internet, “J/K” is text-speak for “just kidding.”)

This summer at Reagle the J/K Tree has become a metaphorical representation of anything that happens onstage when it’s not supposed to.

It began at the start of the summer, with our first show, Into the Woods. The set consisted of a bunch of two-dimensional trees covered in random text from fairy tales, as though they were cut out of the pages of books. Like so:

There were ten trees at various depths and locations, which would fly in in seemingly random patterns to define different areas in the story. In reality, which tree was in which scene was often very important to direct focus and allow access to certain parts of the stage while concealing others. But for the purposes of running the show, there was really no easy way to remember when a certain tree was supposed to fly. You just always had to have the right linesets moving.

Sometimes the wrong tree or set of trees would move. I had a tree-tracking table in a sheet protector on my desk which showed all the moves, the cue numbers, and most importantly, all the trees that were supposed to be in after a given cue had completed. Generally if it was found that a mistake was made, we would just have to deal with it for that scene and assign fly cues so that on the next transition we would end up with all the right trees in.

Until the J/K Tree. The J/K Tree was known to the director and the cast as Tree #2. It was known to the crew as lineset 7. I had to memorize both sets of numbers, which gave me a headache. Anyway, there was one particular transition, on one particular night, when Tree #2 flew in when it wasn’t supposed to. Because it was pretty far downstage, and close to center, it caught attention right away, and I and several other people immediately cried out that it was wrong. But it was coming in like it meant to, and being the center of attention, couldn’t just come halfway in, stop, and then go out. We figured, as we usually did, that we would just have to live with it until the next possible transition. As soon as it landed I mentally scanned ahead in the show to figure out when it could make a graceful exit.

Immediately I realized the problem: this was the transformation scene, where the Witch turns into a beautiful woman. There was a special in the floor that would shine right up at Rachel. I knew the special was just downstage of Tree #2, so her mark for the transformation would be exactly where the tree is. I said, “It can’t be here for the transformation, get it out!” and away it went, almost as soon as it had come in. As it casually returned to the sky, someone on headset commented cheerfully, “J/K!” And from then on it became known as the J/K Tree. Because of the words painted on the trees, we thought it would have been nice if it actually had the letters J and K on it, but I don’t think we ever inspected it that closely.

So through our techs of later shows it’s been the joke when something happens when it’s not supposed to, and is then quickly, and not so subtly, corrected — such as a dramatic light cue called early and then backed out of, or an actor who starts to sing before their cue and then stops — “Oops! Fly in the J/K Tree!”

It’s one of those you-had-to-be-there stories, but I noticed that I used “J/K” in my video in the previous post, and figured I should explain the particular history of it among our crew.


Crazy Sunday Afternoon

I call this: summer stock,theatre — Posted by KP @ 7:38 pm

All we had to do today was a Sunday matinee. After that we have no show until next Thursday. Things have been running smoothly, audiences have been leaping to their feet. When the sun rose this morning, all that stood between us and three-and-a-half days off was two-and-a-half hours of awesome musical theatre.

9:30AM

I’ve already been awake for a while, because somehow I’ve become an early bird like that. My phone rings, and it’s our star. She’s not calling me at 9:30 on a matinee day just to say hi. As I suspected, she wasn’t feeling well. She was calling me to get our producer’s home number to see if she could be rushed in to see a doctor so she could get a prescription before the show. Much to my relief, that was the extent of my involvement, and she was indeed able to see the doctor, and was feeling OK for the show.

12:15PM

I’m about to leave the house. Like packing my stuff. And I get a call from one of the Dynamites. It’s obvious right away it’s train trouble. A large portion of our actors commute on the red line from Boston, and need rides from Alewife, which is the last and nearest station to the theatre. There are two regular pickups: an hour-and-a-half before the show is the Ednamobile, which is driven by our “Edna,” Dan. 15 minutes later is the scheduled departure of the Musicmobile, driven by our music director and keyboard player, also Dan (which is why the two cars have names, instead of “Dan is driving me.”) Anyway, I find out that it’s not just the usual Sunday delays on the red line. Apparently the entire T has been shut down for about 40 minutes due to a power outage. Part of my dismay is that, not being from the area, I really don’t know how to help people when they have train trouble. But I do know that somebody even being slightly delayed on the train can really mess up my day, so all the trains in Boston being shut down less than two hours before a show doesn’t sound good.

I decided that getting to the theatre was not important at the moment, and stayed on my computer trying to reach people who could potentially offer rides, while checking Twitter to see what other Bostonians were reporting about the outage (the MBTA website showed all trains happily running with a green checkmark. Thanks!) Shortly after that, the trains started running again, and our actors (and one of our other keyboard players) made it on, and slowly towards Waltham. The Musicmobile would stay behind for them.

Act I

So finally everybody arrived and the show started without incident. Marissa wasn’t having problems, and I soon stopped worrying about her completely. We had almost gotten through act I when everyone kind of noticed at once that there was something in the air in front of the house right light tree. With all the fake hairspray hanging in the air, seeing particles in the beams of light isn’t anything unusual, but as our board op, Jess, pointed out, there hasn’t been any hairspray sprayed in that area in a really long time. So then the only explanation is that something is burning.

Thankfully this happened at the single point in the show where we have lots of time, during the last scene of the act. There was definitely steady smoke, but even with people looking from all possible angles, nobody was able to tell which instrument it was coming from. The light trees are just in front of the front row on either side and probably contain about 12 instruments each, from about 15-30 feet in the air. We spent the last 10 minutes of the act trying to narrow down the offending equipment, and praying it wouldn’t set off the fire alarm before we could examine it more closely at intermission.

We made it, and soon a good portion of the crew had gathered with flashlights to look at it, and saw nothing. After some debate, we decided it was time to take the inelegant step of bringing a ladder out into the audience. Taking a chance, we got the 16ft. ladder, which was much less disruptive than the A-frame, but wouldn’t be able to reach the top rows of lights, if that’s where the problem was. Basically we just wanted to figure out which light it was so we could unplug it or turn it off at the board.

Most of intermission went by and still no luck. We had our deck electrician on the top of the ladder checking all the connections. We brought all the lights up at 20 percent and he saw no sign of smoke. Finally I said that if we couldn’t find anything we’d have to give up, and suggested we put everything on that tree at full in the hopes that the offending light would show itself. Soon after, the smoke began again. After more looking with multiple sets of eyes on the ground and on the ladder, they found it was coming from a damaged connector. Jess quickly took all the lights out, and the connector was unplugged, and traced to the lights it controlled. That channel was parked out on the board, and soon the ladder was being spirited away backstage.

After the Show

We were pretty exhausted by the time the second act started, but everything went very smoothly for the rest of the show. Then as soon as the show ended, or perhaps as it was ending, the stage right toilet started flooding. Not like kind of backing up, or leaking a little bit. It was gushing water like Niagara Falls. By the time I got there there was at least an inch of water on the bathroom floor, so I wasn’t going in to see exactly what was happening. Two of our stagehands were inside trying to do something, and succeeding mostly in getting soaking wet. Wardrobe, who are based in the room next to the bathroom, and props, who have their tables set up just outside in the hall, produced several tubs filled with towels and we began laying barriers to contain and direct the water away from the props and costumes. The janitor arrived from the lobby, and splashed bravely into the bathroom. Soon we heard cries of, “Leatherman! Leatherman!” coming from inside. I dug into my bag and passed my Leatherman forward. Several seconds later, the sound of rushing water stopped, and the three intrepid plumbers emerged from the bathroom, mission accomplished.

Remarking that in one day the theatre had been attacked by both fire and water, I was getting out of there before the plague of locusts showed up.

I did, however, make a movie about the end of our harrowing day.


August 13, 2010

Hairspray Reading Material and the Joy of Live Theatre

I call this: summer stock,theatre — Posted by KP @ 1:09 pm

Just wanted to share a link about my current production of Hairspray at Reagle Music Theatre of Greater Boston.

The Globe ran an interview with Marissa Perry, who is our amazing Tracy Turnblad. Her story of how she got to Broadway is really inspiring, and actually involved many more twists and turns than described in the article. I described her yesterday during the show as a “quadruple-threat” — acting, singing and dancing, of course, but the threat that’s important to stage managers — she’s really smart and aware on stage, and can recognize and solve problems (like picking up a prop that’s been dropped on the floor, or figuring out how to casually set a brake on a set piece that’s sliding around).

The thing about live theatre that’s tricky is that you can’t always control what will happen on stage, and once it’s in view of the audience, there’s often nothing the crew can directly do to fix it, especially in a show like Hairspray that only has one or two blackouts. Things that get out of place or left on the floor create hazards for dancers, or can cause scenery to get stuck on them. An actor who can be counted on to notice these things and quickly remedy them before they become a problem is incredibly valuable for the smooth operation of the performance. To have a star with that ability, especially one who is almost never offstage, is a great blessing for me.

And I would add to my “quadruple-threat” comment from last night, that she is also a “quintuple-threat,” because on top of everything else, she’s everything you want a performer to be on stage, and she’s nice! It really doesn’t get any better than that.

On the subject of technically-aware actors:
I’ve also been kind of surprised to work with a few directors lately who have specifically taken a moment in rehearsal to talk about the importance of this, by saying things like, “If a prop falls on the floor, don’t ignore it, stay in character and find a way to pick it up. There are other things that need to happen besides your performance, and it’s important that that prop be where it’s supposed to be. You bending down to pick up the prop will not look as bad to the audience as any later problems it might cause.” So I’m grateful for that.

And I will share a story of the best case of an actor saving the day I’ve ever seen:
When I was in college I was the merchandising manager for Jane Eyre on Broadway. There was this scene where Rochester takes Jane out to the garden to propose to her, where there’s a bench on the turntable, and the bench turns off left while Rochester and Jane are kind of walking alongside it, and a scrim flies out revealing the garden. Well on this particular day in previews, I guess maybe the bench had gotten knocked out of place a little on the turntable, and as it spun and the scrim flew, the bottom pipe of the scrim went under the arm of the bench and began lifting it up off the floor by one end. James Barbour, walking slowly past the bench, arm-in-arm with Marla Schaffel, reaches out with his free hand, and casually lifts the arm of the bench off the pipe and deposits it back down on the floor, without missing a step. The combination of reaction time, calmness, and willingness to interact with something (flying benches in his backyard) that was completely out of the realm of the reality of the scene was really amazing.

And finally, if something goes wrong and you can’t fix it, at least come up with a good ad lib, like our Edna, Dan Dowling, did last night:
Somehow he lost a shoe during “Big Dollhouse,” and somehow the shoe ended up in the pit. At the end of the scene, when everybody is released from jail, Dan says his line to the Matron, “You touch one hair on my little girl’s head and I’ll be back to teach you a whole new meaning for split ends,” and then adds, “…and you can mail me my other shoe!” I’m not sure how much the audience laughed because I couldn’t hear anything over the laughter on headset, but suffice it to say, there was laughter all around. He also referenced it again in the next scene where he has an ad-lib spot in the phone call with Mr. Pinky. I think he said something like, “I’ll be right over. But I’ll be minus one shoe” (in that scene he’s wearing slippers). Of course not every show affords such opportunities, but we are lucky to have a show that was intended to have certain spots for ad-libs, and more importantly — a brilliant cast that spends time thinking up good ones, and can also come up with new ones on their feet. It definitely keeps things interesting instead of watching exactly the same show over and over.


August 12, 2010

Hairspray Photo Recap

I call this: summer stock,theatre — Posted by KP @ 1:54 am

Well Hairspray opens tomorrow, and I know I’ve been terrible about blogging. I just finished my work at 1:15AM, and we have a matinee, so I’m unfortunately not going to stay up all night writing, but I have been taking some photos over the last couple days to share.

Here’s one of the many dozens of fun cues I have in “You Can’t Stop the Beat.” There’s one — I swear to God — when Motormouth pulls off her pants disguise revealing her sparkly dress, the cue perfectly represents in moving light the act of taking one’s pants off and throwing them downstage, revealing a sparkly dress.

The cast and crew after our final dress:

(those two above images are production photos, by Herb Philpott)

Our master carpenter, Nat, took on the task of designing the portal which frames the downstage space. He had a cool concept of doing Andy Warhol-like paintings of our Tracy and Link. Well our painters, Jamie and Helen, have spent the last two days recreating photographs of our actors on two flats which sit on either side of the stage. They are awesome.

Head painter Jamie and her assistant, Helen, paint the Link picture, using a projected photo of Nick Peciaro as their guide.

The painting of Marissa Perry installed on stage.

And the usual calling desk photo:


August 1, 2010

Hairspray Load in Day

I call this: summer stock,theatre — Posted by KP @ 7:49 pm

I know I haven’t blogged much about Hairspray yet. Usually that means there are problems, but in this case it’s been going very well. Today we did a stumble-through of Act I, which was very exciting, and made our first serious attack on Act II by staging “Big Doll House.”

Today our set (from Wichita Music Theatre) arrived in two trucks, straight from its closing last night at Gateway Playhouse on Long Island. The tight turnaround between the two rentals has been a great concern for us, but so far so good. We have a lot of backup plans for things.

Just wanted to share some very early photos of the pastel megaliths now crowding our stage and shop.

Miss Teenage Hairspray Scoreboard
Hairpray Set Arriving

The magical giant hairspray can in its travel rack.
Hairspray Can

And the back shop has zero floor space at this moment.
Yeah, That's Enough Storage


July 29, 2010

Backstage at the Vegas Phantom

I call this: theatre — Posted by KP @ 10:55 pm

A reader sent me a link to an article in which one of Vegas’ ballerinas describes a two-show day (because they’re on the casino schedule their shows are shorter and much closer together than on Broadway).

It’s really well written. She perfectly captures the spirit of the little rituals and jokes that develop over the course of a run.

I hope when I get back home I can do one of my own, from my perspective.


July 21, 2010

Here, Have a Funny

I call this: phones,tech — Posted by KP @ 2:17 pm

In light of my recent posts about the iPhone 4 (here and here), I saw this today and had to pass it along.

I love the Steve-and-Bill comics, and if you can’t laugh at yourself for not being able to buy the latest and greatest phone, because it’s possibly not as good as what you already have, what can you laugh at?


July 20, 2010

Huge Hardware Problem Solved (I Think)

I call this: mac,tech — Posted by KP @ 2:00 am

My Macbook Pro needed an exorcism. There was something just not right with it. It’s not like my first Mac, which was a 2002 PowerMac that to this day just spontaneously freezes and kernel panics with no provocation, despite passing every hardware test known to man. It was thankfully more subtle and less disruptive than that.

Let me tell you about how it began. This machine came with 4GB of RAM. My previous machine also had 4GB of (third-party) RAM, of an inferior kind (DDR2 as opposed to DDR3). Knowing how advanced the i7 chip is compared to my 2007 Core2Duo, I expected that with an equal amount of RAM, and literally the same hard drive, this machine would be the same, only faster. Well in real-world use, it wasn’t noticeably faster. In fact sometimes it almost seemed slower. Things that are heavily RAM-dependent (such as boot-up time) were slower. I’ve never sat there with a stopwatch, and I couldn’t actually do a side-by-side comparison, because the hard drive had moved and now I can’t test the original speed of the old computer, but when I originally got the 4GB of RAM in the old machine, I was amazed how fast it booted. This machine was not as impressive.

Parallels

Parallels is a virtualization software that allows you to run Windows (or whatever you want) while booted in Mac OS. It ran terribly on this machine. I mean so bad — so embarrassingly bad — that if there were some incompatibility with i7 MBPs there would be a huge outcry and people would be demanding an immediate patch or their money back. Even when I reduced the RAM and video RAM assigned to the virtual machine to pathetic levels, it was still slow as hell. At a reasonable level (say half the actual hardware capacity) it completely consumed all resources and the computer was totally useless in both OSes. And yet the Parallels user help forums don’t say anything about the current version running particularly badly, or having a problem with the new Macs. So I’d started to become convinced maybe it’s just me.

Quitting Programs

Lately I’ve had a few programs that have been spontaneously quitting upon launch. DVD Player and the text editor WriteRoom seemed to be the most common. Eventually I got WriteRoom running after what I think was a corrupted text file that it kept trying to re-open on launch. But DVD Player still quit on launch sometimes, and then 5 seconds later worked fine. Because of these problems I’ve been looking at Activity Monitor to see if anything looks odd. What I’ve noticed (sometimes connected to the quitting, sometimes not) is an obvious memory leak.

Memory Leak

There was a huge memory leak somewhere. Because of it (and rebooting into Windows for gaming) I have been rebooting my computer usually once a day, so I knew it wasn’t taking very long for the leak to grow to be a GB or more. Of course there are any number of things that could be causing it. Safari and associated plugins can cause problems, or some 3rd-party app could be buggy, but as it’s gotten worse I’ve been using less and less of my apps to try to eliminate possible suspects. I’ve been on Apple’s support forums looking for a large number of complaints of a memory leak, but I didn’t see much that points to a flaw affecting all users of 10.6.4 or anything like that. In one case, a user mentioned that it could be caused by faulty memory, and in light of the history listed above, that’s the first time I started seriously considering a hardware problem.

If I’m having software problems, and not anything really disturbing like kernel panics, I will always blame it on software, but the fact is, I’ve been very disappointed with the performance of this machine since I got it. It’s not worse than my old one, but it’s not better, and lately I’ve been on the verge of looking into getting 8GB of RAM. I almost blogged something about it last week — “since when is 8GB of RAM necessary for a computer to feel fast? ” — but I stopped when I couldn’t find the exact quote from Bill Gates about “640k is enough memory for any computer forever,” and moreover discovered that he probably never even said it, which crushed my ideas for an opening line for the post. The point is, I stopped just shy of going to Crucial and finding out just how much 8GB costs these days, since obviously 4GB is yesterday’s news.

I ran Apple’s extended hardware test and it came out fine. My experience and understanding about the way the universe works is that Apple’s hardware test has never identified a hardware failure on anybody’s computer ever, and is generally considered only a first step to save you time in the case that your hardware is extremely messed up (in which case you probably didn’t need a test to tell you something was wrong), otherwise you need to use more advanced third-party solutions. Which are complicated and if you do it properly, involve booting into single user mode and using the console.

I went back to the Apple forums looking for anything else, and somebody’s post said something like “sounds like bad RAM, make sure it’s properly seated.” Now that sounds really obvious, and in all my experience of bad-RAM-like symptoms in 20 years of using computers, that has never been the problem, but of course it’s one thing to check, sort of like if your toaster won’t work and the first step is “is it plugged in?” And I suddenly realized that I have never reseated the RAM since getting this computer. I opened it up to change the hard drive when I got it, but I never had any reason to touch the RAM. So I figured it couldn’t hurt to pop them out and put them back.

On Mac laptops the two sticks of RAM are one on top of the other. The first one looked pretty normal, but I held out hope that maybe there was some tiny gap not perceptible to the human eye, but that on reseating would make a better connection. I popped it up, and as I pulled it out I couldn’t believe what I saw below it: the second stick was not just maybe-kinda-sorta-not-all-the-way-in. It was sticking up! Generally you put the stick in at about a 30-degree angle and then push it down until it clicks into place on both sides. The stick was at that 30-degree angle, or as far up as it could go with the other stick properly seated on top of it. It was amazing, and explained everything. I have always felt like the computer was performing like it had half the RAM it should, and within a day or two of owning it, I had gone into System Profiler to check, because I suspected that one stick might not be detected. Obviously the connection was made enough that the system reported the 4GB, but in practical use only one stick was doing most of the work.

It’s rather early to say, but the first boot-up was at least as snappy as my old MBP. I assigned 2GB of RAM to Parallels and started it up, and it’s happily and quickly booting Windows XP in the background as I type. I mean easily 20 times faster than it did before — in a few seconds, compared to minutes of freezing the whole computer before I could even get it to abort the whole pathetic attempt at computing. I feel like Parallels is responding faster than Boot Camp does. Which is actually possible, considering that Boot Camp must have been running off roughly 2GB this whole time anyway.

I’m really shocked that the system ran as well as it did for so many months with a problem like that. I have been satisfied with it, but I was disappointed that there wasn’t a noticeable performance improvement compared to a 3-year-old machine, and the particular difficulty it seemed to have with RAM-intensive tasks confused the hell out of me. Now I’m excited to find out just how good of a machine I really have had all along. I’m sure I will need to revisit my review, which was kind of lackluster and unfinished, because I kept waiting for something to be able to point to to say, “Look, this is faster!”

Take for example this summary:

I’ve now had the machine for almost three months, and my assessment is that it’s good but not incredibly noticeable during normal use. Maybe the bottleneck is still the hard drive, and that’s why it feels exactly the same as before. My hope when I bought it was that maybe a year or so later, an SSD drive of respectable size would be available for a reasonable price. And I’m sure sometime around then, 8GB of ram would be really cheap. I haven’t quite mentally grasped the situation of 8GB being a “normal” amount of RAM yet, but when it’s cheap enough, I’ll buy it just because, and maybe I’ll see why. When I bought my last MBP I bought 4GB of RAM (which was relatively expensive at the time) because I was using the machine to run full-motion-video-with-audio projections for Singin’ in the Rain, and it made an enormous difference overnight — just before we opened we increased the resolution of all the videos, and they looked much better, and played much more smoothly. So I’m sure with the quad core and everything else, this thing has more power under the hood that I would find if I was doing more video and other demanding activities.

It’s pretty much all right there: the fact that it’s not faster, the fact that the 4GB of RAM and 7,200rpm hard drive inexplicably doesn’t seem to be enough. It didn’t make sense. And if the solution is that simple, I look forward to changing that review very soon!

And one final thought: I mentioned in my review how I don’t read about benchmarks, don’t perform benchmarks on my own machines, and in general don’t care about more details than “slow,” “fast,” or “OMG really fast!” Well the funny thing is, if I had run some benchmarks on the machine for my review, I probably would have realized right away that it was scoring far worse than published reviews. That’ll teach me.


« Newer Posts — Older Posts »