It would also be nice to hear from Kobo if this bug is being worked on or if this is "working as intended"- so I know whether or not to sell my reader on eBay (because the christing thing can't be returned to the store, only exchanged [what]) and get a Kindle, or hang on to it in hopes of a firmware upgrade.
I really like the reader hardware and Kobo philosophy (who the hell wants to see the web rendered in glorious 16 shade eInk?)... but if they can't get something this utterly basic working on their own format then their resources are probably not concentrated on development as much as they should be, and this is probably a warning sign of things to come.
I read an article somewhere comparing the CEO of Kobo to Apple's Steve Jobs. That's so off the mark it's hilarious. Say what you will about his company's walled gardens and cultish fans and et cetera, but the man is a perfectionist. Kobo seems to be happy just cruising along with something that "mostly works" as long as the money from their eBook stores keeps rolling in. This is depressing considering it seems like they have some talented people designing the stuff who just aren't being utilized in the right way (fix the bugs BEFORE wasting those resources rolling out a new product!). As is usually the case the problem is probably with management.
Last edited by dos; 10-14-2010 at 06:12 AM.
|