![]() ![]() Well I guess it's good for job security, but there is Erlang itself for that already.Īs for the emulator loop which requires computed gotos to be implemented, it could instead be generated from a higher-level description of the opcodes directly to an LLVM IR module, which would be faster to compile because the CFG would be less silly written by hand. ![]() ![]() Rewriting something in C++ in the year of our lord of 2017 isn't the smartest move when there are better tools available. Suffers from fundamental structure and human incompatability issues.Ĭ++ would never avoid crappy things from happening, such as silly data races because someone used a static variable in the middle of nowhere. Not as though Erlang is implemented in an obfuscated style of C++ that Replacement would be a massive, end-of-Netscape type upheaval. Is an alternative to, but not a replacement for, the current runtime.Ĭompeting runtimes occasionally expose hidden benefits. Of the OTP team itself) would enjoy working on a rewrite in Rust that I can imagine that some of us (probably including some Well explored runtime known to such a large team would be rewritten toĪ new language. I really can't imagine such a large, old, well documented, Implementation and performance improvements would become more obviousĪnd safer to implement over time. Thing for the OTP maintainers and that, in particular, new feature Those coding in Erlang is that maintenance would become more of a sure But what would it improve for the programs written in Erlang ![]() > It may or may not simplify working on the VM and may or may not make it > Any thoughts on the benefits existing Erlang programs would get from a ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |