On Sat, Jun 19, 2010 at 09:48:19PM +0200, VOITPTRPTR wrote: > To be honest, I've no knowledge on how Lucene core is implemented.
Naivete can be helpful for some tasks, such as reviewing documentation and APIs for clarity -- see the wiki page I put up earlier today at <http://wiki.apache.org/lucy/BrainLog>. > But I'm pretty confident when coding in C (portabilty, clarity, refactoring > ...). > More over I've strong background on algorithms and algorithms optimization. Certainly those are valuable skills. Some parts of Lucy have been highly optimized, but there's a lot of room for improvement and a lot of known inefficiencies. Lucene has focused on optimization much more than we have, so we get to study what they've done over the last couple years and apply the lessons they've learned. Up till now it's been more important to emphasize modularity and information hiding so that the system we build can *withstand* optimization without becoming an impenetrable rat's nest. > Is it possible to ask questions about design choices of Lucy (how indexes > are built, algorithms behind the scene...) in this mailing list as I'm > missing this Information Retrieval skills? There will be many opportunities for such conversations, particularly since a lot of indexing classes are going to get submitted to JIRA over the next few weeks. When code gets submitted for inclusion is an ideal time to comment. Personally, I enjoy giving long-winded answers as much as the next person, but I've learned that I have to control my impulse to bloviate and invest my time in ways that yield maximum return. The more you contribute, the more you will get back. Marvin Humphrey
