 |
lua-l archive |
|
|
||
|
|
Hi Alex, On 2/21/12 10:50 AM, Axel Kittenberger wrote: We had a very friendly guy from super secret Intel and CERN institutes at the Lua workshop who could not tell us what he was doing but his background was top notch future mega multi core high speed research:... stuff more interesting. Be it multi-threading, multi-processing or distributed computing. With efforts like this, Lua might nibble on that wave, albeit its own design near zero caters for anything like that There is one thing that is currently still hidden from programmers: the cores do not really share cache memory, that is transparently replicated, which hits a road block at some point. I thought this is what will make cores more independent of each other, share less, and maybe demand more intelligence. Lua might be eyed to migrate to the micro level. There is Elixir, a Ruby-like syntax on top of the Erlang JVM.My own preference currently would lie into something that like Erlang or Clojure (or other functional languages) has immutable datastructures by default, but be just a little more imperative than these to hit my taste. https://github.com/josevalim/elixir "Elixir is a programming language built on top of Erlang. As Erlang, it is a functional language with strict evaluation and dynamic typing built to support distributed, fault-tolerant, non-stop applications with hot swapping. The main difference between Elixir and Erlang is its more natural homoiconic syntax that supports meta-programming. Elixir also supports polymorphism via protocols (similar to Clojure's), dynamic records and a reference mechanism. Elixir and Erlang share the same bytecode and data types. This means you can invoke Erlang code from Elixir (and vice-versa) without any conversion or performance hit." Henning |