Well, I believe that you guys have seen improvements compared to the existing Unity runtime; I don't necessarily believe that the improvements are just because you're going from IL -> C++ -> Native instead of IL -> Runtime. How is the performance of a C# function through your compiler vs a C# function compiled with MS's compiler and running in .NET 4.5? Or through the latest Mono? I'm concerned that you could get the same (or better) performance increase by just updating to a newer compiler and runtime rather than writing your own. I guess that's fine; I was hoping that this announcement was going to finally be the announcement about the solution to the Mono problem, but I guess this isn't it. This doesn't really solve anything from your users' perspective as far as garbage collection, incompatibility, or being long overdue for a .NET upgrade. To me, it just seems to introduce even more instability and unknowns into garbage collection, incompatibility, and the potential of ever seeing a .NET upgrade. I get this, but the solution I was hoping for was that you guys would leverage the decade's worth of work that Microsoft and Mono have put into .NET, not write your own from scratch.