It robs us of many optimization opportunities on the CLR. Java Lucene compiled using IKVM will not perform as well as a native port. Think async/await, BCL data structures, different GC considerations (LOH for example), etc. There's also the issue of supporting PCL, Mono, Mobile and Azure natively. Just to name a few.
I've had a chat with the lead developer of IKVM and promised to run an IKVM version head to head with the native port once we are done. -- Itamar Syn-Hershko http://code972.com | @synhershko <https://twitter.com/synhershko> Freelance Developer & Consultant Lucene.NET committer and PMC member On Thu, Feb 5, 2015 at 2:43 PM, Omri Suissa <[email protected]> wrote: > Hi, > > It looks like it takes a lot of time to manually port Lucene to .net (still > in version 3), why not using ikvm to port (at least as a base line and > improve from there)? > > > What are the disadvantages of ikvm in this case? > > > Thanks, > > Omri >
