We're not talking about a quantum leap here (the smallest possible discrete movement that is still definably a motion), but more like a largish step forward. Babbage Linden reports that the last major showstopper issue with the Mono common language runtime appears to be solved.

Babbage's primary concern was with memory usage of the Mono runtime engine, which kept increasing over time. Normally that memory would be given back when the runtime terminated, but there are always scripts running in a simulator, so the runtime would only terminate when the simulator restarted or shut down (which it would, a good deal sooner with the script runtime continuing to hungrily consume increasing amounts of memory).

Well, the good news is that -- with the aid of a number of memory and code tracing tools -- Babbage was able to provide enough information to Mono developers Zoltan Varga and Paolo Molaro to isolate and correct the memory growth issues.

This brings the Mono runtime to a point where it can start to be seriously deployed as a substrate for other systems, including (eventually) LSL scripts. Integration of the Mono system will now be commencing in earnest.