Post by Eduardo Julian on Jul 24, 2021 18:31:32 GMT
Hello, everybody.
I'm happy to announce that I'm done doing all the major work on Lux 0.6.
All that is left at this point is updating the documentation, updating the book and a few aesthetic tweaks I'd like to do now to avoid breaking the syntax in the future.
I expect to be done with it by the end of August, so you can expect the 0.6 release on mid-to-late August.
I know that I have a horrible track record forecasting when Lux 0.6 will be done, but given that all the hard work is finally done with, I think that even if I miss the mark, it won't be by much.
Wish me luck
Sadly, I was not able to get Lux to run in all the new platforms I wanted.
In particular, the PHP implementation was pretty solid, but there was some uncertainty due to bugs in the PHP interpreter I was using that I didn't think it would be wise to release it.
I plan to resume work on it in the future once I have access to a suitable replacement.
The Common Lisp and R implementations have a similar story to the PHP implementation.
The Scheme implementation will be postponed indefinitely, since the Scheme interpreter I was using (Kawa) served me well during compilation, but then I faced challenges using it post-compilation, and using other Scheme interpreter/compilers was even more of a challenge. I feel that the Scheme ecosystem is so fragmented and inconsistent that it might be a bad idea to try to target Scheme for now.
The good news, though, is that we're definitely getting JavaScript, Python, Ruby and Lua compilation on this release.
I'll also be releasing a new JVM compiler, fully written in Lux itself, which works better than the old Clojure-based compiler and runs just as fast.
Working on 0.6 has taken more time than all previous versions of Lux combined, and over 2/3 of all the commits I've made to the Lux project; but the pay-off is close at hand.
I'm happy to announce that I'm done doing all the major work on Lux 0.6.
All that is left at this point is updating the documentation, updating the book and a few aesthetic tweaks I'd like to do now to avoid breaking the syntax in the future.
I expect to be done with it by the end of August, so you can expect the 0.6 release on mid-to-late August.
I know that I have a horrible track record forecasting when Lux 0.6 will be done, but given that all the hard work is finally done with, I think that even if I miss the mark, it won't be by much.
Wish me luck
Sadly, I was not able to get Lux to run in all the new platforms I wanted.
In particular, the PHP implementation was pretty solid, but there was some uncertainty due to bugs in the PHP interpreter I was using that I didn't think it would be wise to release it.
I plan to resume work on it in the future once I have access to a suitable replacement.
The Common Lisp and R implementations have a similar story to the PHP implementation.
The Scheme implementation will be postponed indefinitely, since the Scheme interpreter I was using (Kawa) served me well during compilation, but then I faced challenges using it post-compilation, and using other Scheme interpreter/compilers was even more of a challenge. I feel that the Scheme ecosystem is so fragmented and inconsistent that it might be a bad idea to try to target Scheme for now.
The good news, though, is that we're definitely getting JavaScript, Python, Ruby and Lua compilation on this release.
I'll also be releasing a new JVM compiler, fully written in Lux itself, which works better than the old Clojure-based compiler and runs just as fast.
Working on 0.6 has taken more time than all previous versions of Lux combined, and over 2/3 of all the commits I've made to the Lux project; but the pay-off is close at hand.