On Fri, Aug 23, 2013 at 2:23 PM, David Jeske <[email protected]> wrote:
> I'm particularly curious how you think bitc-the-second differs from > Nemerle1/2, since it has modular compilation, inference, variants, > pure-functional, and compile-time-metaprogramming. > Since I can't find a proper language reference for Nemerle, I'm not sure how to answer that. I looked at their web site. It leaves me with more questions than answers about Nemerle. > AOT may be no big deal in your mind, but the fact is that there exists >>> not open source optimization infrastructure that attempts to target >>> garbage-collected languages. >>> >> > Mono seems darn close to an open-source implementation of an AOT > optimization infrastructure (which admittedly could use work, but it's > quite capable and even supports LLVM as a backend for AOT). > Yes. And since LLVM doesn't track type information for registers, it's not a particularly good target for GC'd languages. The problem with Mono performance is interesting. It's very possible that >> two or three people, contributing actively, could make a huge improvement >> in Mono performance. But as you note, the JIT implementation in mono was a >> fairly small fraction of the effort. It's not at all out of the question >> that one could simply build a new and better JIT and re-use most of the >> library infrastructure investment that Mono has already made. > > > This seems true. I think there is just proportionally less open-source > activity around CLR because the main end-user system supporting CLR is > Windows. Compare that to the Javascript community, where there are several > competing runtime scrambling to each re-add the same performance > optimizations (including PIC). > > I think this is already changing because of mono-team's work on their > excellent Xamarin/Mono C# mobile development direction. However, this is > more focused on Mono/LLVM/AOT since AFAIK iOS does not allow JIT. > Yes. There is an allergy to C# in the open source community because of its connection to Microsoft. What you say about Xamarin may be true, but it surprises me. My own experience has been that the Mono development process has become noticeably *less* open since the Xamarin transition. Even things as simple as building the latest open source version of the mono tool chain or MonoDevelop have ceased to be documented. And of course Xamarin itself is heavily committed to closed-source development as a source of revenue. shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
