4 ms·

I'm not sure I buy the notion of, "Solves the two language problem." There is always going to be some library or environment consideration that makes a unified

I'm not sure I buy the notion of, "Solves the two language problem." There is always going to be some library or environment consideration that makes a unified language for everything impractical (unless your entire business runs on an AS400).

andlrc 9y ago
> unless your entire business runs on an AS400 Even there you got support for C, C++, Java amung others as well as the whole IBM family (RPG/ILE, CL, REXX, ...) With somewhat decent bindings in RPG.
rattray 9y ago
They have a pretty good reputation for FFI to most complements, IIRC. eg; https://docs.julialang.org/en/stable/manual/calling-c-and-fortran-code/ https://docs.julialang.org/en/stable/manual/calling-c-and-fo... https://github.com/JuliaPy/PyCall.jl https://github.com/JuliaPy/PyCall.jl
ffriend 9y ago
The two language problem is more specific to scientific computing where literally every popular library is written in more then one language - fast C/C++/Fortran and convenient high-level R/Matlab/Python. NumPy, SciPy, Caffe, Theano, Tensorflow to name a few. I once had to rewrite Matlab + C code (for face tracking) to pure Julia - not only the resulting code was almost twice smaller, it also ran ~20% faster.
- dnautics 9y ago
  I wrote a library in c to replace a Julia one I wrote (and make it more portable) and found that the c version was slower! (Couldn't inline functions as easily in c and was also being more parsimonious about memory usage in c)