I hadn't heard from my estranged son for a couple of years, so I had a cop buddy run a search for him. Turns out he was in a Russian prison, charged with killing a government official. Since this could be it for him, I decided to go see him at his trial.
As I'm waiting at the court house, there's a huge explosion, and who do I see escaping in the confusion? You got it - my son, along with a Russian dissident! I steal a truck, and follow the gang of thugs who are trying to kill him. After crashing into about a thousand other cars and stealing another vehicle, I save him from the bad guys. As I'm giving him hell, I discover he's not really a criminal - he's CIA!
Of course, the bad guys crash our safe house, somehow miraculously missing us with all the machine guns, and we make our escape. After some close calls, we steal another car and catch the bad guys, foiling their nefarious plot. My son and I trade wisecracks throughout, and bond between dodging bullets. The world is once again safe for democracy!
What's that you say? You aren't buying this story? That's OK - I know you're shocked, but this didn't really happen. I've just given you the plot to the latest of the "Die Hard" movies - A Good Day to Die Hard.
I'm not a big fan of violent movies, but this Bruce Willis series is fun - filled with plenty of cartoon-style smashups. You always know John McClane (Willis) will be OK in the end. There are plenty of dead bodies, but they're mostly bad guys, so who cares, right? This one is typical of the series - McClane lives through beatings, car crashes, and gunfire that would kill any normal human. Of course, the trademark wisecracks flow as swiftly as the bullets.
Does this movie sound silly and illogical? Do you have trouble believing the McClanes can arrive at Chernobyl in their stolen car just moments after the Russian crooks in their helicopter? Do you find it unlikely they'd be able to survive massive gunfire, and avoid local police? Of course you do - this movie is not realistic in the slightest! You know what else? It doesn't have to be. This is a fantasy - like any super hero story, you need to disconnect your disbelief and just enjoy the show. John McClane, like Superman, Spiderman, or The Green Lantern, exists in another universe - where men can fly, walk on walls, or get the living hell beat out of them while cracking wise.
As long as you're willing to accept the realities of his world, you'll find this to be an entertaining movie. The plot, if you can call it that, is OK. Willis is fun as the aging McClane. Everybody else is forgettable. There's no deeper meaning, no hidden message to it. Good guys win, bad guys die, I eat popcorn and enjoy the action. Yeah!
Search This Blog
Thursday, February 21, 2013
Friday, February 8, 2013
Warm Bodies - Movie Review
I like zombies.
Check that - I should say I like zombies in the movies and TV shows. I don't personally know any zombies, so I 'm not sure what I would think of them if I met one in person. I suspect I wouldn't like them much, but a new movie, Warm Bodies, is out that may change my mind. I've watched a couple of entertaining and funny zombie flicks (Zombieland and Shaun of the Dead come to mind), but I had yet to see a zombie love story. This move changes that!
"R" (Nicholas Hoult) is a zombie, and the story is told from his point of view. We hear his inner monologue, which is much more eloquent than the grunts and growls he is able to express out loud. R can't remember his name, and knows something is missing, but he just can't seem to get it out. He and his "best friend" - played by veteran character actor Rob Corddry - can't communicate, but hang out together, making this one of the strangest buddy films of all time.
R knows something is missing, but just can't put his finger on it. That all changes when he and a group of fellow zombies attack a scavenging party of survivors. R kills and eats the brain of Perry (Dave Franco), gaining some of his memories in the process. Perry's girlfriend, Julie (Teresa Palmer) is also there, and some of the residual feelings from Perry's brain cause R to save her from the other zombies.
Nothing that follows will surprise you, as R becomes more and more lifelike as he takes care of Julie. There are some funny bits as R struggles to communicate, a confrontation with Julie's father (John Malkovich), and a climatic struggle between good and evil - just an ordinary day in the life of a zombie.
Warm Bodies isn't a great movie. It's dumb, and the logic of it breaks down if you're paying attention, but this movie isn't about paying attention. It's a unique concept, and has some really funny moments. It's a great send up of movies like the Twilight series, which have humans romantically involved with vampires and werewolves. If that can happen, why can't your daughter hook up with a zombie?
You could make a case that the zombies lovers represent same sex or mixed race couples, but really, if you're looking for deeper meaning here, you're missing the point. This is a funny movie, more in the tradition of The Naked Gun than Guess Who's Coming To Dinner. Don't expect to learn anything - just relax and enjoy the fun.
Check that - I should say I like zombies in the movies and TV shows. I don't personally know any zombies, so I 'm not sure what I would think of them if I met one in person. I suspect I wouldn't like them much, but a new movie, Warm Bodies, is out that may change my mind. I've watched a couple of entertaining and funny zombie flicks (Zombieland and Shaun of the Dead come to mind), but I had yet to see a zombie love story. This move changes that!
"R" (Nicholas Hoult) is a zombie, and the story is told from his point of view. We hear his inner monologue, which is much more eloquent than the grunts and growls he is able to express out loud. R can't remember his name, and knows something is missing, but he just can't seem to get it out. He and his "best friend" - played by veteran character actor Rob Corddry - can't communicate, but hang out together, making this one of the strangest buddy films of all time.
R knows something is missing, but just can't put his finger on it. That all changes when he and a group of fellow zombies attack a scavenging party of survivors. R kills and eats the brain of Perry (Dave Franco), gaining some of his memories in the process. Perry's girlfriend, Julie (Teresa Palmer) is also there, and some of the residual feelings from Perry's brain cause R to save her from the other zombies.
Nothing that follows will surprise you, as R becomes more and more lifelike as he takes care of Julie. There are some funny bits as R struggles to communicate, a confrontation with Julie's father (John Malkovich), and a climatic struggle between good and evil - just an ordinary day in the life of a zombie.
Warm Bodies isn't a great movie. It's dumb, and the logic of it breaks down if you're paying attention, but this movie isn't about paying attention. It's a unique concept, and has some really funny moments. It's a great send up of movies like the Twilight series, which have humans romantically involved with vampires and werewolves. If that can happen, why can't your daughter hook up with a zombie?
You could make a case that the zombies lovers represent same sex or mixed race couples, but really, if you're looking for deeper meaning here, you're missing the point. This is a funny movie, more in the tradition of The Naked Gun than Guess Who's Coming To Dinner. Don't expect to learn anything - just relax and enjoy the fun.
Wednesday, February 6, 2013
Russian Amerika - Book Review
Russian Amerika is an alternate history novel written by Stoney Compton. This is the first book I've read by Compton, who apparently uses Alaska as the setting for most of his tales. Sometimes, authors feel the need to set the stage for their alternate history stories by showing the exact divergence from our timeline. Compton takes a different - and, I think, correct - tack by just presenting it as it is and not trying to fill in all details. We know this world is different from our own, we just don't know exactly what happened. That's OK with me - the world is described well enough to follow the action, so that's all I need.
In Russian Amerika, the Czar still rules in Russia, the United States lost the Civil War, and North America is split into 9 or 10 smaller entities. The political situation isn't well defined by the book, but the United States and the Republic of California appear to be allies, and support the revolution that is trying to form the new republic in Alaska.
The action centers around Gregori (Grisha) Grogorievich, a former officer in the Russian equivalent to the French Foreign Legion, who is thrust into the middle of the conflict by circumstances. What follows is a good adventure yarn, taking us through the revolution.
Technology in this universe is somewhat behind that of our world - late 1980's in the book feels more like 1940 - no jets, limited communications, less sophisticated military equipment. Because of this, the rebels, led by Native Americans (the Dena) have some success against the Russian forces.
Grisha is a good protagonist - tough and smart. Circumstances throw him together with the Dena, eventually leading to his important role in the revolution. The Dena are superb woodsmen, fierce warriors, and loyal friends, so it's easy to root for the revolutionaries.
I like Russian Amerika, but it's not perfect. The characters are interesting, but quite black and white. Every rebel is altruistic and heroic, while the Cossacks are universally evil, with no redeeming qualities whatsoever. Other Russians are mostly incompetent, except those who convert to the rebel's cause. Speaking of turncoats, everyone - with one exception I can think of - who goes over to the rebel side is completely converted, and instantly becomes a trusted, valuable member of the revolt. The Dena Indians are almost superhuman, possessing incredible fighting and tracking skills, and able to withstand torture without cracking.
The battle sequences are entertaining, but a bit hard to believe. Small, ragtag bands of heroic guerrillas succeed by sabotage and subterfuge, not by fighting pitched battles with enemy infantry when they're badly outnumbered and outgunned. To be fair, the rebels get some valuable help, which makes this a little easier to believe, but it still seems as though their success comes a little too easily. To me, it would be a bit more believable if the technology level was lower - say about equal to that availble during our Civil War. That would even up the playing field a little, and make the rebel's victory more plausible.
I'd also like to see more character development. Grisha is a three-dimensional character, but many others are less fleshed out. I'd like to see a sympathetic Cossack - not agreeing with his superior's methods, but powerless to do anything about it. In any revolution, there are good and bad guys on both sides - I'd like to see a little more of that.
All that being said, this is still an entertaining yarn. There are a lot of interesting characters, and the action certainly keeps your attention. In many ways, it reminds me of Eric Flint's 1632 series (although that is a better book, IMHO), in that it presents an extremely optimistic view of the events. That's OK - we know this isn't a history book, and who's to say it COULDN'T go like that? If there's no great message behind this story, it's still fun to read. There's at least one sequel, which has the potential to further develop characters and plot lines. This is a simple book that tells an entertaining story - worth the time if you like an adventure story.
In Russian Amerika, the Czar still rules in Russia, the United States lost the Civil War, and North America is split into 9 or 10 smaller entities. The political situation isn't well defined by the book, but the United States and the Republic of California appear to be allies, and support the revolution that is trying to form the new republic in Alaska.
The action centers around Gregori (Grisha) Grogorievich, a former officer in the Russian equivalent to the French Foreign Legion, who is thrust into the middle of the conflict by circumstances. What follows is a good adventure yarn, taking us through the revolution.
Technology in this universe is somewhat behind that of our world - late 1980's in the book feels more like 1940 - no jets, limited communications, less sophisticated military equipment. Because of this, the rebels, led by Native Americans (the Dena) have some success against the Russian forces.
Grisha is a good protagonist - tough and smart. Circumstances throw him together with the Dena, eventually leading to his important role in the revolution. The Dena are superb woodsmen, fierce warriors, and loyal friends, so it's easy to root for the revolutionaries.
I like Russian Amerika, but it's not perfect. The characters are interesting, but quite black and white. Every rebel is altruistic and heroic, while the Cossacks are universally evil, with no redeeming qualities whatsoever. Other Russians are mostly incompetent, except those who convert to the rebel's cause. Speaking of turncoats, everyone - with one exception I can think of - who goes over to the rebel side is completely converted, and instantly becomes a trusted, valuable member of the revolt. The Dena Indians are almost superhuman, possessing incredible fighting and tracking skills, and able to withstand torture without cracking.
The battle sequences are entertaining, but a bit hard to believe. Small, ragtag bands of heroic guerrillas succeed by sabotage and subterfuge, not by fighting pitched battles with enemy infantry when they're badly outnumbered and outgunned. To be fair, the rebels get some valuable help, which makes this a little easier to believe, but it still seems as though their success comes a little too easily. To me, it would be a bit more believable if the technology level was lower - say about equal to that availble during our Civil War. That would even up the playing field a little, and make the rebel's victory more plausible.
I'd also like to see more character development. Grisha is a three-dimensional character, but many others are less fleshed out. I'd like to see a sympathetic Cossack - not agreeing with his superior's methods, but powerless to do anything about it. In any revolution, there are good and bad guys on both sides - I'd like to see a little more of that.
All that being said, this is still an entertaining yarn. There are a lot of interesting characters, and the action certainly keeps your attention. In many ways, it reminds me of Eric Flint's 1632 series (although that is a better book, IMHO), in that it presents an extremely optimistic view of the events. That's OK - we know this isn't a history book, and who's to say it COULDN'T go like that? If there's no great message behind this story, it's still fun to read. There's at least one sequel, which has the potential to further develop characters and plot lines. This is a simple book that tells an entertaining story - worth the time if you like an adventure story.
Tuesday, January 29, 2013
How to Install Your Dishwasher
When we moved, we had a lot of work done on the new house - remodeling virtually every room. We bought all new appliances when we did the kitchen, but we have been very disappointed with our Frigidaire dishwasher. Although it was supposed to be a quality unit, it didn't work as well as we expected - certainly not as well as the one in our old house. In addition, it was awkward to load, and the shelf adjustment wasn't handy. After fighting it for almost 6 months, we decided to cut our losses and get a new one.
The folks at Lowes were very helpful, giving Theresa a good deal on a high-end dishwasher - almost half price. They delivered it while I was out of town for a couple of days, so I was ready to install it a week ago.
The easiest installation is like mine - when you're replacing an existing dishwasher, you've already got water, a drain line, and power available. If you didn't have a dishwasher before, you'll need to do some prep work first:
The folks at Lowes were very helpful, giving Theresa a good deal on a high-end dishwasher - almost half price. They delivered it while I was out of town for a couple of days, so I was ready to install it a week ago.
The easiest installation is like mine - when you're replacing an existing dishwasher, you've already got water, a drain line, and power available. If you didn't have a dishwasher before, you'll need to do some prep work first:
- Determine your desired location. Most of the time, you'll want to be close to the sink - that makes it easy to hook up your water and sewer lines, as well as making it handy to load dishes. Often, you'll be able to remove a base cabinet to make room, or you may be able to install the dishwasher at the end of a row of cabinets. If you don't have room to install a built-in dishwasher, you may want to consider a portable unit, so you can just wheel it in place when you want to use it. If possible, install the built-in model - you'll like the performance and ease of use.
- Locate the nearest water and sewer lines available, and get connections set up. In most cases, you can "T" off of your existing water supply line - making sure to add a shut off for the dishwasher. You drain line will usually go into your disposal, if you have one (don't forget to knock the plug out of the inlet), or into a special inlet on the drain tail piece. If your dishwasher is going to be more than 6 feet from your drain line, you may need to consult a plumber for installation.
![]() |
| If you don't have a disposal, you'll need this special tail piece with a side inlet - available at any hardware store. |
- You'll need electrical power to the dishwasher, as well. You should plan on having a circuit just for the dishwasher - if you don't have one, you'll need to add it (many homes have the dishwasher on a shared circuit, either with kitchen lights or the disposal, and it may work OK, but it's better to do it right and add the circuit). If you're not comfortable with electrical work, hire an electrician to do it. If you're pretty handy, a you should be able to handle it.
- Turn off the power and water to the old dishwasher, and unhook them. Unhook the drain hose underneath the sink, as well.
- Locate the screws holding the dishwasher into the cabinet (probably in the front of the unit, going into the counter top), and remove them. Slide the dishwasher out of the way.
- Measure the opening height, and adjust the legs on the bottom of the new dishwasher so that it fits the opening. You'll be able to adjust a little later, if necessary, but it's a lot easier to get it close now. If your floor is very uneven, you'll need to fix that before proceeding - a small amount can be corrected with the feet on the bottom of the unit.
- Check your connections to the new dishwasher to make sure you've got everything you need.
- Hook up the water supply line, drain line, and electrical power (making absolutely certain that the power is still shut off at the breaker) to the dishwasher.
- Slide the unit partially into place, making sure to route the water and electrical lines as needed.
- Hook up the water, drain, and electrical connections at the source, if you haven't already done so.
- Finish sliding the dishwasher in place. Check to make sure it's level and raised up so it fits just under the counter top - adjust the feet on the bottom of the unit as needed.
- Secure the dishwasher to the counter top or cabinets using the included brackets and screws. Make sure the screws are not too long, or they'll protrude through the counter top!
- Turn on the water and electrical power, run a cycle, and check for leaks.
Thursday, January 24, 2013
My WiFi Adventure
A long time ago - we're talking pre-Internet times - if you had a home computer, you probably had a modem in it. A modem allowed your computer to communicate over phone lines with other computers. You could, theoretically, transfer files to another modem-equipped computer, after making sure both were online and using complementary protocols. More often, you could log on to "bulletin boards" and download shareware programs - games, utilities, etc. that you could try first, then pay for.
Now, of course, virtually every computer is connected to the Internet. Early on, most computers connected with a modem and phone line. Later, wired broadband connections were the standard. Today, your Internet connection is most likely delivered to your home via DSL or Cable, then made available to various devices (computers, printers, tablets, smart phones, video receivers, etc.) over a wireless network.
Modern devices search for wireless access, and automatically connect to known networks, assuming you've got your device set up to do so. The whole thing works very well, and makes smart phones, tablets, and laptops truly portable. Wifi networks are readily available - most restaurants have them - so you can be connected almost anywhere.
Most wireless networks are stable and secure. Networks at public venues may not have security installed, so you may be slightly more susceptible to hackers - do your banking in secure locations. My problem came with our home network.
We moved a few months ago. In our old home, our router was located in my office in the basement. Our main TV was also in the basement, where the Wii was connected - important because we needed the wireless for online gaming or movies using this gaming system. The only connectivity issue we had was with a net book computer we used in the kitchen - the signal strength was weak, causing slow connection speeds. Overall, that was a minor issue, since we weren't doing anything important on the small computer anyway.
In our new home, our main TV is on the main floor. In addition to the Wii, we now have a Roku, with which we watch many old movies on Netflix or Hulu. We've also both got iPads, so our data needs are increased significantly. Since our router is located downstairs, in the corner of the basement opposite the living room, the weakest signal in our network was the room where most of our needs were. As a result, we were experiencing a number of "drops" where we'd lose the network in the middle of whatever we were doing (most often watching a movie or TV show). Clearly, a change was needed.
My first reaction was to buy a new router. Our old one was a mid-level router, designed for average users. I bought a higher end router - still not top-of-the-line, but better - designed for "medium to large homes with higher data needs". This worked better, but after some time, we began experiencing the same issues as before. Figuring we just didn't have enough signal strength, I bought a new, higher-end router, and a range extender. This would do it for sure, right?
I set up the new, hot shot, dual band, extended range router downstairs, then placed the range extender upstairs in our spare room, directly above the router. After some fiddling around with the settings, I got connected, and everything looked great. Then I walked into the living room! My powerful signal from the bedroom was only marginally better than the downstairs signal, still weaker than what I needed. I grabbed the extender and moved it out to the living room. Now, I had it! I was able to connect to the router, and the signal to my video devices was perfect. The only issue was that the extender was sitting in the middle of the living room - not coordinating well with Theresa's decorating.
This was an easy problem to solve, right? I just moved the extender a few feet over so it was sitting by the TV - hidden from casual view like all the other components. Finally, we were ready to relax and enjoy a movie - and we did, for about 3 minutes. At that point, the movie stopped to reload, running for a couple of minutes each time before pausing again. What happened?
It turns out that moving the range extender just a few feet had put it on the edge of our network's range, causing a very slow connection. It was confusing, because our Roku said the signal strength was "Excellent". Engaging my brain - something to which I'm unaccustomed - led me to realize that the signal FROM the booster was strong, but the signal TO the booster was marginal. This was like using a bucket to move a teaspoon of water - it works OK, but you don't really get anything accomplished.
Clearly, a new approach was needed. I debated the purchase of another new router, this time going for a super high-end unit. I suspect that would work - after all, many restaurants have a strong signal that will reach even into the parking lot. After some thought, I decided to just run a network cable up behind the TV, and install a router there. This wouldn't be difficult, since our basement isn't finished, and it would have the added advantage of allowing for a wired connection to devices, should that prove necessary.
Since I had our old router sitting around doing nothing, I decided to leave the new one in place, and add the old one upstairs. We'd now have three wireless networks on our system - the original, now relocated upstairs, and two emanating from the dual band router in the basement. I could have just moved the router up, but, since I've got a computer and printer downstairs, I figured it would be handy to have network access down there.
After the requisite false starts and screw-ups - during which I lost ALL connectivity throughout the house - the system was ready to go. With relatively little trouble, I was able to connect all the devices upstairs to the network, and give it a try.
So far, everything seems to be working fine. The wireless network is a bit slower than wired, but it's certainly within acceptable limits. Watching TV and movies is easy - there are no objectionable delays. My Wii has an Ethernet connection port, so I may experiment with a hard-wired connection there, to see if there is a big improvement in performance. The Roku is wireless only, but similar devices are available with Ethernet connections, so if it looks like it's worth it, I can switch that out, as well.
I suspect wireless technology will continue to improve, so that Ethernet cable will be unnecessary in the future. Indeed, I'm sure we'll one day have universal coverage, so that every device will be connected at all times. Until then, we'll have to keep patching and improving our home networks to keep up with our ever-growing data needs.
Now, of course, virtually every computer is connected to the Internet. Early on, most computers connected with a modem and phone line. Later, wired broadband connections were the standard. Today, your Internet connection is most likely delivered to your home via DSL or Cable, then made available to various devices (computers, printers, tablets, smart phones, video receivers, etc.) over a wireless network.
Modern devices search for wireless access, and automatically connect to known networks, assuming you've got your device set up to do so. The whole thing works very well, and makes smart phones, tablets, and laptops truly portable. Wifi networks are readily available - most restaurants have them - so you can be connected almost anywhere.
Most wireless networks are stable and secure. Networks at public venues may not have security installed, so you may be slightly more susceptible to hackers - do your banking in secure locations. My problem came with our home network.
We moved a few months ago. In our old home, our router was located in my office in the basement. Our main TV was also in the basement, where the Wii was connected - important because we needed the wireless for online gaming or movies using this gaming system. The only connectivity issue we had was with a net book computer we used in the kitchen - the signal strength was weak, causing slow connection speeds. Overall, that was a minor issue, since we weren't doing anything important on the small computer anyway.
In our new home, our main TV is on the main floor. In addition to the Wii, we now have a Roku, with which we watch many old movies on Netflix or Hulu. We've also both got iPads, so our data needs are increased significantly. Since our router is located downstairs, in the corner of the basement opposite the living room, the weakest signal in our network was the room where most of our needs were. As a result, we were experiencing a number of "drops" where we'd lose the network in the middle of whatever we were doing (most often watching a movie or TV show). Clearly, a change was needed.
My first reaction was to buy a new router. Our old one was a mid-level router, designed for average users. I bought a higher end router - still not top-of-the-line, but better - designed for "medium to large homes with higher data needs". This worked better, but after some time, we began experiencing the same issues as before. Figuring we just didn't have enough signal strength, I bought a new, higher-end router, and a range extender. This would do it for sure, right?
I set up the new, hot shot, dual band, extended range router downstairs, then placed the range extender upstairs in our spare room, directly above the router. After some fiddling around with the settings, I got connected, and everything looked great. Then I walked into the living room! My powerful signal from the bedroom was only marginally better than the downstairs signal, still weaker than what I needed. I grabbed the extender and moved it out to the living room. Now, I had it! I was able to connect to the router, and the signal to my video devices was perfect. The only issue was that the extender was sitting in the middle of the living room - not coordinating well with Theresa's decorating.
This was an easy problem to solve, right? I just moved the extender a few feet over so it was sitting by the TV - hidden from casual view like all the other components. Finally, we were ready to relax and enjoy a movie - and we did, for about 3 minutes. At that point, the movie stopped to reload, running for a couple of minutes each time before pausing again. What happened?
It turns out that moving the range extender just a few feet had put it on the edge of our network's range, causing a very slow connection. It was confusing, because our Roku said the signal strength was "Excellent". Engaging my brain - something to which I'm unaccustomed - led me to realize that the signal FROM the booster was strong, but the signal TO the booster was marginal. This was like using a bucket to move a teaspoon of water - it works OK, but you don't really get anything accomplished.
Clearly, a new approach was needed. I debated the purchase of another new router, this time going for a super high-end unit. I suspect that would work - after all, many restaurants have a strong signal that will reach even into the parking lot. After some thought, I decided to just run a network cable up behind the TV, and install a router there. This wouldn't be difficult, since our basement isn't finished, and it would have the added advantage of allowing for a wired connection to devices, should that prove necessary.
Since I had our old router sitting around doing nothing, I decided to leave the new one in place, and add the old one upstairs. We'd now have three wireless networks on our system - the original, now relocated upstairs, and two emanating from the dual band router in the basement. I could have just moved the router up, but, since I've got a computer and printer downstairs, I figured it would be handy to have network access down there.
After the requisite false starts and screw-ups - during which I lost ALL connectivity throughout the house - the system was ready to go. With relatively little trouble, I was able to connect all the devices upstairs to the network, and give it a try.
So far, everything seems to be working fine. The wireless network is a bit slower than wired, but it's certainly within acceptable limits. Watching TV and movies is easy - there are no objectionable delays. My Wii has an Ethernet connection port, so I may experiment with a hard-wired connection there, to see if there is a big improvement in performance. The Roku is wireless only, but similar devices are available with Ethernet connections, so if it looks like it's worth it, I can switch that out, as well.
I suspect wireless technology will continue to improve, so that Ethernet cable will be unnecessary in the future. Indeed, I'm sure we'll one day have universal coverage, so that every device will be connected at all times. Until then, we'll have to keep patching and improving our home networks to keep up with our ever-growing data needs.
Monday, January 21, 2013
Mike Johanns Responds to Me! (Kind Of)
A month ago or so, I posted about Nebraska's Mike Johanns and his vote against the U.N. Disabilities Treaty. At the time, his justification for his cowardly vote was his supposed concern for the sovereignty of our country - a flimsy excuse at best. I also noted that I had sent him a critical email, but didn't expect an apology, or even a response, from him.
I have to admit, I was wrong! Checking the mail after the first of the year, I noticed a letter, addressed to me, explaining his vote. I should note, the letter had my name on it, and it addressed my concerns, but it was a form letter. Apparently, Johanns got enough complaints about his vote that a response was prepared.
In any case, reading the letter was enlightening. I now discover that his vote was not his fault - it was Harry Reid's fault! Wow, Reid is something, isn't he? He's such a scary character - you can just picture republicans all over the country scaring their kids with, "If you're not good, Harry Reid will get you"! Johanns now says he voted against the treaty because he told Reid not to bring up any treaties before the end of the session, since there wouldn't be time to read and study them adequately. Riiiiight........ I'm certain that's the reason - it couldn't be that you're a cowardly hypocrite who doesn't have the guts to just come out and say you did what you did for purely political reasons.
In reality, the treaty had nothing to do with U.S. sovereignty, and everything to do with a Republican party playing to their base. Voting against it had nothing to do with Harry Reid, and everything to do with avoiding a primary challenge from the right. Mike Johanns should save the effort, and quit trying to convince me he's trying to do his job.
I have to admit, I was wrong! Checking the mail after the first of the year, I noticed a letter, addressed to me, explaining his vote. I should note, the letter had my name on it, and it addressed my concerns, but it was a form letter. Apparently, Johanns got enough complaints about his vote that a response was prepared.
In any case, reading the letter was enlightening. I now discover that his vote was not his fault - it was Harry Reid's fault! Wow, Reid is something, isn't he? He's such a scary character - you can just picture republicans all over the country scaring their kids with, "If you're not good, Harry Reid will get you"! Johanns now says he voted against the treaty because he told Reid not to bring up any treaties before the end of the session, since there wouldn't be time to read and study them adequately. Riiiiight........ I'm certain that's the reason - it couldn't be that you're a cowardly hypocrite who doesn't have the guts to just come out and say you did what you did for purely political reasons.
In reality, the treaty had nothing to do with U.S. sovereignty, and everything to do with a Republican party playing to their base. Voting against it had nothing to do with Harry Reid, and everything to do with avoiding a primary challenge from the right. Mike Johanns should save the effort, and quit trying to convince me he's trying to do his job.
Saturday, January 19, 2013
Blogsy test
This is a test post using Blogsy, a new blogging tool I'm trying for the iPad. If it works well enough for me to use it, I'll review it in a future post. For now, I'll just try some basic formatting, as well as some other features
You should be able to add links http://garthright.blogspot.com/2013/01/a-powerful-anecdote.html?showComment=1358655038091&m=1, but I don't know how to do it yet.
Subscribe to:
Posts (Atom)

