Google Drive Failure

Google Drive is a failure.

Google Drive was released yesterday, and I clicked the button on the website letting Google know I was interested in their product. I received an email late last night informing me that my Google Drive was ready. This morning, on a lark really, I went to the Google Drive website and clicked on the download link for the sync application to add to my work iMac. I downloaded the DMG fie without a problem and opened it up. I copied the Google Drive app to my Applications folder, like you are supposed to with Macintosh, and then I sat back and marveled at it. Google Drive, finally.

I’ve been a loyal Dropbox customer for years and back in January I sprang for the $100 a year expansion of my Dropbox up to 50GB. Everything I use connects to my Dropbox via the Dropbox API and just for the record, I am totally in-love with Dropbox. There is no reason for me to leave them as a customer. But even if you are loyal, it doesn’t mean you can’t explore. I have a professional account with Box.com through my work, and we arranged that after drop.io was consumed by the wraiths at Facebook. I have a personal Box.net account with 50GB but I don’t use it because Box only allows sync with paid accounts, so it’s not worth my while. Google Drive was just along these lines, just another option to look into.

So I started Google Drive on my iMac and I was asked to authenticate, something I expected. Then nothing. I started the app again and nothing. I opened up the Console app and here is what I found:

4/25/12 7:17:44 AM Google Drive[22481] *** __NSAutoreleaseNoPool(): Object 0x2e2ba80 of class OC_PythonString autoreleased with no pool in place – just leaking

4/25/12 7:17:44 AM Google Drive[22481] *** __NSAutoreleaseNoPool(): Object 0x2e37440 of class OC_PythonString autoreleased with no pool in place – just leaking

4/25/12 7:17:44 AM Google Drive[22481] *** __NSAutoreleaseNoPool(): Object 0x2e332f0 of class NSCFString autoreleased with no pool in place – just leaking

4/25/12 7:17:44 AM Google Drive[22481] *** __NSAutoreleaseNoPool(): Object 0x2e32600 of class NSCFString autoreleased with no pool in place – just leaking

4/25/12 7:17:45 AM [0x0–0x221c21a].com.google.GoogleDrive[22481] 2012–04–25 07:17:45.119 Google Drive Icon Helper[22488:903] Inject result: 0

So, it’s broken. This isn’t the first time a new app was built that failed horribly on my iMac. If anyone cares, and perhaps if anyone from Google is reading, this is a standard 2009–2010 iMac running Mac OSX 10.6.8. The only thing different about this particular Mac is that the account has it’s home on an AFP-connected OD-domain’ed Apple xServer. A network home. This causes headaches for Adobe Acrobat Reader so it’s probably the reason why Google Drive collapses on startup.

Since I can’t run the application, and since it wasn’t designed elegantly to take into account those people who have network-based computers like mine – unlike Box.com’s sync app or Dropboxes sync app, I can only state that Google Drive is not ready for prime time. Google Drive is not ready to compete in the marketplace and Google has to go back to the drawing board and try again.

SmashBurger Kalamazoo – A Return

Last Friday my friends Justin and Jeramiah asked to try SmashBurger Kalamazoo. For them it was the first time, for Scott and I it was our return. I promised that I would give SmashBurger Kalamazoo another shot around September 11th, 2010. I was a little late in getting back to the restaurant to give it another try. This was tounge-in-cheek because a beloved family member of mine sent my blog entry to the restaurant management company and they responded quickly, urging us to return and give SmashBurger Kalamazoo another shot.

Upon our return we dwelled for a brief few moments in the foyer to the entrance while our friends regarded the menu items. After we all made up our minds, we walked into the restaurant. The order process was acceptable, the person behind the counter was stumbling and trying to cope with our order but got it in successfully. In comparison to our previous visit there were some notable changes:

  • Fountain Service was at 100%
  • Restaurant was not absolutely packed.
  • Manager was not bounding like a billiard ball.
  • Servers were not wandering aimlessly asking everyone what they ordered, the numbering system is working.
  • The hamburgers were rested properly and did not fragment or run with juice.

That being said, quite an improvement. However there were some lingering problems and one I did not detect until this last visit. We were dining with my dear friend Jeramiah, who I trust completely when it comes to food preparation. He detected it before I did, and that is that the French Fries had a different taste to them. They were fried, but they carried an odd flat/dull taste along with them. Jeramiah told us that what we tasted was what happens when you deep fat fry french fries in shortening instead of a true plant oil, like Peanut. It wasn’t unpleasant, just different.

In the end we couldn’t detect any failures in SmashBurger itself on our visit, our only point of surprise was the price, again. For Scott and myself it came to $18.57. For Jeramiah and Justin it came to $21.52. I polled the table and posed the same question to them that I did the last time: Comparing SmashBurger Kalamazoo to Culvers Kalamazoo, which one would you choose and why? The answer was unanimously for Culvers, and the reasons were “better food” and “cheaper prices”. The prices for what we got were really remarkably upsetting, still.

Of course, for due diligence I must also state that Jeramiah became extremely ill the next day and had to miss work because he was very ill. The illness was most likely foodborne as it affected his digestion. I can’t pin anything on SmashBurger as none of the other of us got sick, but my trust in a restaurant is savaged when I or someone I know gets sick from eating at a place. Once bitten, never again.

That being said, we are done with SmashBurger Kalamazoo. We will never return to this restaurant and we won’t include it when we are thinking about places to go when we are hungry. The food is not very compelling for the price and the prices themselves are too high.

Entertainingly, the people who own and run SmashBurger Kalamazoo also run at least two other “Food Traps”, FireBowl Cafe and Wine Loft. While I haven’t been to FireBowl Cafe and wouldn’t comment on the quality or price, I did attend Wine Loft’s inaugural opening and I have not been back since. The food quality follows the design that we see in SmashBurger Kalamazoo, meh food for unacceptably high prices. Seeing that two out of the three properties this holding firm own are off-limits, it makes it a handy guide to figure out whatever else they own and avoid that out-of-hand. We can simply assume it’s not very good for too much money, and instead patronize other establishments that are better and worthy.