I like this trend toward wide-spectrum languages. For other recent examples, see Terra and Nimrod (I realize Nimrod has been around for a while, but seems like it's recently gaining significant popularity).
It's nice how closely languages like Python and Lua and integrated C through their various FFIs (particularly Luajit's FFI), but it's still a huge pain in the ass to continuously context switch between languages whenever you have to drop down and do something low-level, or to improve performance. I hope at least one of these languages catches on in the wider programming community so I'll have a chance to use it in "real world" programming.
Wow, this blows my mind up, thanks for posting. Immediately had a look if it was already discussed on HN and to my surprise it went completely unnoticed! So here the links:
Indeed (author here). Aside from Fibonacci being a worthless benchmark, the Common Lisp code was unoptimized and running on CLISP(!) on Windows(!!). Moreover, it was from an old version of the compiler. The benchmark just sat there for a while as I rewrote it from C++ in Common Lisp, and it was stupid of me to let it hang around for so long.
Yes, it's strange to benchmark a standard and not an implementation. Besides, timing in well-known implementation such as SBCL looks much better here than in the chart.
How hard is it to extend 'foreign' to other languages besides C/C++? If this is possible, a guide for doing so would be invaluable. It would be awesome if there was a lisp that could compile directly to LLVM using native objectiveC libraries on iOS. VERY cool work, thanks for sharing!
That was part of my original intention. The reason 'foreign' takes C as its first argument in the examples is so I could eventually add support for binding mangled C++ functions mangled through Clang/GCC (Which luckily use the same mangling scheme).
I feel there is a spot between the performance and control of low-level languages and all the tremendously useful features of high-level languages. What I basically wanted was "C with Lisp macros". I think Rust is the closest language, ideologically, to Hylas.
There is no specification or anything very formal laid out except for a couple .md files in the docs folder. The language has evolved and changed a lot over the past year (Everything from the comments to the type system has changed), and is nowhere near prod-ready, but I want to eventually put it to practical use.
[+] [-] jnbiche|12 years ago|reply
It's nice how closely languages like Python and Lua and integrated C through their various FFIs (particularly Luajit's FFI), but it's still a huge pain in the ass to continuously context switch between languages whenever you have to drop down and do something low-level, or to improve performance. I hope at least one of these languages catches on in the wider programming community so I'll have a chance to use it in "real world" programming.
[+] [-] bakul|12 years ago|reply
[+] [-] reirob|12 years ago|reply
https://news.ycombinator.com/item?id=5397123
https://news.ycombinator.com/item?id=5125339
[+] [-] agumonkey|12 years ago|reply
[+] [-] eudox|12 years ago|reply
[+] [-] phaer|12 years ago|reply
[+] [-] j_m_b|12 years ago|reply
[+] [-] eudox|12 years ago|reply
[+] [-] 286c8cb04bda|12 years ago|reply
You might be interested in http://programming.nu/
[+] [-] wukix|12 years ago|reply
intro talk (at Bay Area Lisp Revival): https://wukix.com/mocl-balisp8
[+] [-] unknown|12 years ago|reply
[deleted]
[+] [-] hwh|12 years ago|reply
[+] [-] eudox|12 years ago|reply
I like to pretend it looks more like 'hylas' than 'aylas'.
[+] [-] wes-exp|12 years ago|reply
[+] [-] eudox|12 years ago|reply
There is no specification or anything very formal laid out except for a couple .md files in the docs folder. The language has evolved and changed a lot over the past year (Everything from the comments to the type system has changed), and is nowhere near prod-ready, but I want to eventually put it to practical use.