For part I, click here.
Where is Reia in the development cycle? When will it be Beta/Production Ready?
You can consider it to be in an “early alpha” stage at this point.Â There are a number of open tickets for known issues on our ticket tracker.Â While there are a small number of tests many parts of the language are completely untested. The goal is to implement a specification/testing tool similar to MSpec (http://github.com/rubyspec/mspec/tree/master) and using that to create an executable specification of the language itself.Â Once this is underway the language should effectively be “beta”. Unfortunately there are still some additional language features needed before such a tool can be written, like simple inheritance.
How will releases work - with multiple, frequent releases similar to the Rails cycle, or a slow release cycle focused on a ‘perfect 1.0′ similar to Django?
I would like to develop the language iteratively as opposed to the boil-the-oceans approach seen in Python 3000, Ruby 2.0, Perl 6, and C++0X.Â This is easy when a language is new and here’s little concern about breaking compatibility with existing programs, since there aren’t many.Â However I think even entrenched languages have managed to do it successfully.Â C# comes to mind.
How can a developer get involved and contribute?
If you’re interested in Reia, join the mailing list:
Also, consider forking Reia on github:
Once you’ve forked a copy, take a look at the open tickets on Lighthouse:
Try capturing one of the known defects with a (failing) test, and if you can try to fix it.Â Once you’ve captured a bug in a test, or better yet fixed the bug and made that test pass, send me a pull request on Github and I’ll merge your changes back into my branch.
Or, just try using Reia.Â The test coverage right now is fairly poor, and many defects have been discovered just by people trying to use the language.Â If you find a problem, open a ticket on Lighthouse and I’ll try to get it resolved.
Thanks again, Tony!
Categories: Blogs Erlang Inside
Erlang on Twitter
» ckeithray (C. Keith Ray): “How and Why We Switched from Erlang to Python at Mixpanel Engineering” http://t.co/ocrVplHaY7
“How and Why We Switched from Erlang to Python at Mixpanel Engineering” http://t.co/ocrVplHaY7
» JesitaMinenarto (Jesita Minenarto): @ErlAng_fei Rse iya..
iya,pasti tk doain..
@ErlAng_fei Rse iya..
» rioherwanto (Rio Herwanto): PHP level dewa erlang. XD RT @ajialfian: Yeee, BBM batal multiplatform…
PHP level dewa erlang. XD RT @ajialfian: Yeee, BBM batal multiplatform…
» ErlAng_fei (Erlina Anggraeni Fei): Wele.. Gak liat internet ae? Tanggal 1 aku ._. RT @JesitaMinenarto: Blum kluar hsilnya,br nnt jam 3 hsil nya kluar..km tggl brp?RT
Wele.. Gak liat internet ae? Tanggal 1 aku ._. RT @JesitaMinenarto: Blum kluar hsilnya,br nnt jam 3 hsil nya kluar..km tggl brp?RT
» JMayrbaeurl (Juergen Mayrbaeurl): @richorama Spent a whole day last year to get #RabbitMQ running on #WindowsAzure Cloud Services. Difficulties just came from #Erlang
@richorama Spent a whole day last year to get #RabbitMQ running on #WindowsAzure Cloud Services. Difficulties just came from #Erlang
» Chelseaangela13 (ChelseaTan (谭梅灵)): @ErlAng_fei oo harus itu!! Wkwk :p
@ErlAng_fei oo harus itu!! Wkwk :p
Number of aggregated posts: 10651
Most recent article: May 21, 2013
» Moraru on This is Why You Spent All that Time Learning to Program: It is true that computer science was a pain in the back at time that i’ve had to learn it…
» Commercial hand dryers on Couchbase Meetup at new HQ: Buy online from here where you will get so much of variety in Commercial hand dryers for people. If you…
» Fort McMurray Homes on Motivated Reasoning and Erlang vs Python vs Node: I don’t really understand why this post is motivational? I don’t even see a post, just a title. Fort McMurray…