[erlang-questions] Why do "interface to language X" projects all seem to die out?

Michael Truog <>
Wed Aug 31 20:46:49 CEST 2016


py_interface is GPL, which may explain less use
(I did https://github.com/okeuday/erlang_py/ to make sure I had a BSD licensed dependency)
edtk depended on an obscure scripting language
(I did https://github.com/okeuday/GEPD/ to get EDTK functionality that only depends on the preprocessor, however clang doesn't like boost preprocessor yet, haven't needed to add NIF generation to it)

Other interface to language X projects that are alive include
http://cloudi.org (C/C++, Erlang/Elixir, Java, JavaScript/node.js, Perl, PHP, Python and Ruby)
https://github.com/okeuday/erlang_rb
https://github.com/okeuday/erlang_js
https://github.com/okeuday/erlang_pl
https://github.com/okeuday/erlang_php

On 08/31/2016 07:18 AM, Matthias Lang wrote:
> Hi,
>
> Pretty much all of the "not built in to OTP" ways to connect to other
> languages seem to have died, i.e.
>
>     - EPI (C++). Last commit 2009.
>     - py_interface (Python). Last commit 2014. Freshest of the lot.
>     - edtk (C). Last release 2007.
>     - dryverl (C). Last release 2008.
>     - erlua (Lua). Project page dead. Author's email is dead.
>     - erlualib (last commit 2010). Github-linked company page dead.
>
> Can anyone offer some experiences or ideas why?
>
> Could it be that these types of solutions are rarely needed? Maybe
> NIFs are unbeatable for the "narrow interface, no state, high
> performance" cases and port programs with hand-rolled interfaces most
> of the rest.
>
> Matt
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions
>



More information about the erlang-questions mailing list