Agree, of course there's some bias. I think the problem here is he's judging the entire framework based on a one-off demo I put together for the Netflix data set, which is hardly a good example. The review even notes this. The review then goes on to judge the result accuracy based on performance of one algo on one data set. Hmm.
The parts about memory usage are dead on, and that's what I have tried to fix recently -- I have driven it down about 40% at least. The comment about not having a truly distributed recommender is right on too. I don't know what algo they are using but have some sense of it -- makes some sense. The big part they are overlooking is their approach is completely offline. This rather misses the point of any interesting CF application in my view, which all involve something far more real-time. I don't really understand the criticism about a CF framework "only doing CF". On Mon, Aug 3, 2009 at 3:20 PM, Grant Ingersoll<[email protected]> wrote: > Saw this on Twitter the other day in regards to Taste: > http://www.iletken-project.com/index.php?option=com_content&view=category&layout=blog&id=34&Itemid=59&lang=en > > Would be useful to learn from it where possible (there is also some likely > bias inherent in, since the vendor sells their own solution). I suspect > with some of the work Sean is doing in terms of refactoring right now, that > a lot of this will change in the near future. > > -Grant
