News for hackers. Stuff that matters.

A comment on Languages on BEAM, the Erlang virtual machine. Parent comment

Re:Languages on BEAM, the Erlang virtual machine by dozzie on Saturday January 21, 2017 @01:06PM (#13451229)
> I understand that it runs on BEAM, much like I understand that IronPython runs on the CLR.

Those are different cases. Your question is more like "what is faster: C or Fortran?" than "what is faster: C or Python?".

> However, IronPython's performance is slower than C#'s performance due to the dynamic nature of the language

No. It's slower because IronPython is an interpreter, while C# compiles to byte code, not because one is statically typed and the other is dynamically typed.

[ Parent | on HN ]
Re:Languages on BEAM, the Erlang virtual machine by braveo on Sunday January 22, 2017 @03:24PM (#13457200)
https://en.wikipedia.org/wiki/Dynamic_Language_Runtime#Archi...
[ Parent | on HN ]
Re:Languages on BEAM, the Erlang virtual machine by dozzie on Sunday January 22, 2017 @05:46PM (#13458099)
And what does it have to do with the fact that Python is interpreted by IronPython, which obviously slows down code execution?
[ Parent | on HN ]
Re:Languages on BEAM, the Erlang virtual machine by braveo on Sunday January 22, 2017 @11:04PM (#13459676)
the DLR was specifically created to avoid that approach, IronPython, et al, haven't used such an approach since the DLR was released.

It dynamically generates IL which is then JIT'd.

[ Parent | on HN ]