Quote:
Originally Posted by nekokami
That's what really annoys me. It's bad enough that iRex has failed to support the iLiad to the extent that they promised, but they've made it much harder than necessary for anyone else to pick up the slack.
|
That's certaily a valid frustration, but how many of the other eInk companies even allow users to pick up the slack? Do any of the others openly allow user community development and open source most of their software? I don't know.
Quote:
|
If they're going to abandon any further development for the iLiad, as seems very likely, I hope they'll at least consider releasing source on the Content Lister so the community developers can fix it.
|
I agree that would be great. Not only fix the content lister as it stands, but with enough information about the hardware interaction between that code and the iLiad, it should be possible to clone some functionality of the new DR1000 UI.
Quote:
|
But I, for one, am going to wait until they've got the product to a state where I think it would be usable as-is before buying, or recommending that anyone else buy.
|
Yep. Absolutely good advice, no matter what product/company you're talking about. I think a lot of people lost sight of that with the iLiad, and are now mad that it didn't fulfill their expectations for additional features. If you bought it because of what it could do at the time, then you're a lot less likely to be upset now.
I think many people are finding that they've learned that lesson the hard way. Personally, I bought mine a year and a half ago with software version 2.9.5 (?), and was happy with it then. 2.10, 2.11 and 2.12 were just bonuses as far as I'm concerned. Yeah, I'm disappointed that development isn't going to continue, but I don't feel ripped off about it.
Moral of the story: Don't rely on undeveloped features to justify the purchase cost.