Agree on this improve an existing runtime or fork something like rust anything else you need very deep pockets.
I dont think the JVM is easier to adopt .. things like Iron Python went very easily onto the CLR. The issue with the CLR as i have mentioned is mono is slow and backwards and few in the Research/ language design space develop on windows. Ben On Fri, Aug 23, 2013 at 1:42 AM, David Jeske <[email protected]> wrote: > > > Personally I think there is more room for finding a better optimization of > execution-and-productivity shoehorn down path #2. IMO, the JVM world has > already shown it's much easier to adopt languages based on JVM, and > superset JVM runtimes, than it is to adopt independent systems. CLR just > happens to have more features conducive to systems programming. > > However, this is all academic at this point. Today these comments can be > interpreted as support for Shap's decision to use CLR as a temporary > target. When bitc-the-second is usable on CLR, it can be interpreted as > encouragement to attempt a CLR-superset, rather than abandon the CLR > community ecosystem entirely. >
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
