I've always thought that ebook readers were a little goofy. E-ink was an interesting technology, but the readers seemed to be there just to give the screens a reason to exist, not to actually solve a problem that anybody actually had. Why would anybody want to read on an electronic device, when they could just read the actual book, which would no doubt be a better experience? I had read a couple of books on my computer or my PDA over the years, and never really found it to be as satisfying an experience as reading the actual paper copies.
Obviously, my opinions have changed. I had a chance to play around with both a Kindle and an older-model Sony Reader (PRS-505) over a weekend back in March, and was quite surprised. I had heard that e-ink screens were nice to read on, but these were just incredible. I was expecting something like my old grey scale Palm screen; readable even in bad light, but nothing to write home about. However, the e-ink screens on those two devices were really quite impressive. I read quite a bit on the two devices (mainly on the Sony Reader, I liked the device a lot more than the Kindle) over the course of that weekend, and decided to buy one for myself.
After I did the research, I ruled out everything except for Sony's offerings. In short, the Kindle was too expensive and non-open... and all the other options don't exist, so far as Canada is concerned. Easy decision, I guess. The only hard part was choosing between the Sony Reader Touch or the Sony Reader Pocket. I tried both out at LD, and ended up going with the Pocket. It was $100 less, though it sacrificed the touch screen (obviously), card reader, music playback, and a couple other things that I don't remember and can't be bothered to look up (in-line dictionary and photos, I think). Basically, everything but book reading. The thing is, pretty much every other device I have already plays music and has a touch screen. All I really wanted was an ebook reader. And between the two, the Pocket Edition was by far the better for reading, at least to my eyes. The Touch touch layer added a nasty glare that the Pocket didn't have, and I really didn't want to deal with that. So the Pocket Edition it was. Of course, there have been price drops and new products and all sorts of other things going on in the ebook market that makes my carefully-researched decision woefully out of date, but I still think I made the right choice, and I still have a darned good ebook reader.

This is either blue or black, depending on who and when you ask. Right now, I say it's blue.
Okami is one of those many games that sit in the "Awesome games you have never played but should" category. Over the last little while I have been trying to get through some of those games, playing Beyond Good and Evil (Varied gameplay and a lot of fun) and Psychonauts (Not quite my cup of tea, but still quite good). I didn't expect to get stuck for so long on a single game, though. Okami is a weird case in that it's a wonderful game that I really really want to love, but I can't actually bring myself to play.
In a nutshell, Okami is beautiful, charming, and innovative. However, it is also long, frustrating, and derivative.
Note: If you are seeing this line, it has been nine months since I started writing this post and it has been put up in its unfinished state. It seems, like the game itself, I just can't find the energy or motivation to finish it. Perhaps I'll get back to it one day...
It has been almost two months since I made the post about the trouble with my Android phone on Rogers (or any post, for that matter; things have been busy...). This is the inevitable follow up to that. About a week after I made that post, I finally got fed up with the official Rogers ROM (slow, crashing, non-standard UI, everything I mentioned in the last post), and decided to install a more up to date custom ROM. Rogers had just released an online waiver that would allow people running custom ROMs to keep their data service, so it was an easy decision. The rest of this post outlines the headaches that resulted from that. In a nutshell, I talked to Rogers six times and was without data for about three weeks.
I recently had to deal with tech support for two totally different companies on two totally different issues. They were two totally different experiences. I offer them both up as a contrast. Plus, I want to complain about Rogers.
First Issue: Dead Roomba, iRobot
My poor robo-buddy just up and died some time around the New Year. It stopped charging, giving no response whatsoever to being plugged in or to any of the buttons. No rhyme or reason, jut got up one day and decided to not work. I was not impressed, I had only had it since October. I did some testing using the charger and battery from somebody else's Roomba, and determined that it was the robot itself. Great. To make matters worse, I dropped my Roomba while I was working on it, snapping the front wheel assembly clean off.

This is not good.
I contacted iRobot support via their web page and explained the situation, my accident and all. After a couple diagnostic questions, they decided to replace my robot, charger, and battery. Outright. With a better model, with more features, with no cost to me. They even gave me an upgraded 'fast' charger and let me keep the old robot/battery/charger to use as spares (well, they suggested recycling it, like that's going to happen).

I think that went well.
So to iRobot customer service, I say good job. Excellent job, in fact. At best I was expecting them to have me ship it in for repair or perhaps ship me a bare-bones replacement and have me ship the dead one back minus the accessories. Shipping me an upgraded unit is certainly going above and beyond. I just hope the new robot lasts longer than the first one.
And dirt detection is an awesome feature. I don't know how it works or how reliable it really is, but I love it.
Second Issue: Mandatory Android Update, Rogers
Now this is a totally different beast; It requires some back story. A bug was discovered in Android 1.5 back in September that prevented 911 calls under certain circumstances. Google fixed it, T-Mobile issued an OTA patch with the fix in October and they moved on. Rogers, with the exact same phones running pretty much the exact same software, ignored the problem until last week. When they finally realized the problem existed on their phones, they issued a quick software update for the Magic that both fixed the problem and included the promised Sense UI update. OK, fine. A little late perhaps, but at least they got an update out and including a promised major software update at the same time. The problem came in when they decided to make the update mandatory... and cut off the data for everyone that didn't upgrade. Because that makes sense.
Now the problem is that I don't want to run their upgrade. I'm perfectly happy with the software I have on my phone. In fact, their upgrade would actually downgrade my phone from 1.6 to 1.5, losing all sorts of neat features that I like (new market, faster camera, new map/nav, Google Goggles, and so on and so on). In return I would get... a non-standard replacement for the default UI (which I happen to like). That would be like Shaw cutting off your cable internet because they wanted you to apply an update to Windows XP after you moved on to Windows 7, and they refuse to reconnect you until you can prove you've done it.Time to talk to Rogers.
So call number one. I give them a ring, sit on hold for about fifteen minutes, talk to some fellow named Henry or George or Alfie or something like that, and explain the situation. I've already upgraded to 3rd party software, the 911 problem is already fixed on my phone, I don't want to run their update, and so on and so forth. Hank hems and haws, checks with 'level 2' and finally tells me that I'll be fine, as I am running a newer version than the one that has the problem. No guarantees, but my data should not be cut off when the deadline rolls around. That is exactly what I wanted to hear, so I thank him and go about my business.

Kind of pretty, but so very much not worth it.
Then Sunday rolls around and I have no data. Fun times. I did read in several places that they may be cutting off data to everybody - even those that did the official update - for a minimum of 24 hours. Fine, I'll let it wait. Two days later, no data. Of course, data is 90% of what I use my phone for, the actual 'phone' functionality is secondary to the ability to search the internet and check my email. Time for call #2. This time I'm on hold for well over an hour. When I finally get through (to Craig or Brian or Morty or something), the conversation pretty much consisted of me saying I don't want to run their downgrade for something that doesn't effect me and him saying that there was nothing he could do about it, so just install the update and deal with it. He tried to make it sound like he was breaking some giant rule by suggesting I could re-root my phone after the data was updated, but it was clearly just an attempt to get me to go away.
So... I 'updated' my phone. I took the long route in order to make sure it didn't give the perfected SPL (much harder to root later), and installed Rogers's terrible ROM. Long story short... it is terrible. Slow, buggy, non-standard. Cool features from 1.6 don't work and nothing it adds are worth it. HTC's Sense UI is alright, though very dark (and slow, laggy, and so forth). I may tough it out until the 2.1 update hits just to give it a chance (and to make sure Rogers doesn't cut me off again), but I definitely prefer the stock UI.
So all in all from Rogers? A terrible experience with idiotic customer service practices combined with incredibly unhelpful phone support. The end result is me having a slower phone with less features than I had a month ago, all to 'fix' a problem I didn't have.
They should have just sent me a robot.
December was crazy, but January is slowly getting better. I finally found some time to finish this post, which has been sitting half-completed for well over a month, so LUCKY YOU.
Once I finished my first Zelda stitch, I went back to the series that I started with, Super Mario Brothers. The logical next game to do was Super Mario Brothers 2, the bizarre non-Mario Mario game that was actually a modification of the Japanese Doki Doki Panic created when it was decided by Nintendo that the 'real' SMB2 was too hard for western gamers. Interestingly, SMB2 (the North American version) was the first one I ever played, and one of the few games on the NES that I actually played to completion. It's still a little weird, though.

Turnips? Seriously?
I really like the colors in this one, particularly the greens and reds (which yes, do make up 85% of the piece). Mario looks a little washed out, but he does in the actual game as well.

Yup, a turnip.
This was a fair bit easier to stitch than both the first Mario and the first Zelda, partially due to the size. It's also the first one that I did where all the elements are connected, so no counting of blank spaces was required, which removed a lot of the difficulty. It was a fast project, but I really like the results. It's possibly one of my favorites of all my video game projects. Plus, the lowest level of the ground reminds me of Dad's brand chocolate chip cookies, so it has that going for it. Here's the gallery, plus some highlights in all-new Can't-Be-Bothered-To-Line-Them-Up Vision!

So very red... but not a turnip. Radish, perhaps?

Turnip Action Man Strikes!

He is so doomed. Referring, of course, to that poor turnip.

There could be anything under there! Anything! It's probably just another turnip, but it could be ANYTHING!