On 22 August 2013 00:48, David Jeske <[email protected]> wrote: > > On Aug 21, 2013 6:32 AM, "Bennie Kloosteman" <[email protected]> wrote: >> I dont see the JVM or CLR going anywhere , JVM is like 18 years >> ...nothing close to these run times and they are expensive build. .Latest >> trends seems to be more native compiling. ( via C or via IR) Haskell , >> Rust , Go , Microsoft are going back to native ( winrt and even talk of C# >> to native) .. > > IMO - It is very important to distinguish runtimes where binary shared > libraries can be compatibly updated- as only these systems can be used for > os-level system libraries. > > Once you include this criteria, it becomes clear that C, Objective-C, JVM, > and CLR are virtually the only games in town. > > Most of the rest are whole program compilers which must be built on system > libs from one of those other primary environments. (Ocaml, Go, Haskell, D, > C++, etc)
I really can't figure out what you're trying to say here, can you elaborate on the problem? My initial guesses were: * something about ABI compatability of shared libraries * something about system bootstrapping -- William Leslie Notice: Likely much of this email is, by the nature of copyright, covered under copyright law. You absolutely may reproduce any part of it in accordance with the copyright law of the nation you are reading this in. Any attempt to deny you those rights would be illegal without prior contractual agreement. _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
