Live data from Hacker News

Elixir v0.5.0 released

elixir-lang.org

1–10 of 21 posts

Re: Elixir v0.5.0 released

#5

I really wish projects like this would put together a basic, downloadable document on their language. Something that tells the reason and acts as a tour of the language.

As an example to this, I really like the xtend docs: http://www.eclipse.org/xtend/#extensionmethods

Re: Elixir v0.5.0 released

#6
post #4

Is it me or a release notes with a list of what changed is nowhere to be found?

Although it doesn't have a complete list of changes you can check some changes in the blog.

http://elixir-lang.org/blog/

There are some posts with a little summary of what happened during the week.

Re: Elixir v0.5.0 released

#7

I really wish projects like this would put together a basic, downloadable document on their language. Something that tells the reason and acts as a tour of the language.

As an example to this, I really like the xtend docs: http://www.eclipse.org/xtend/#extensionmethods

This is a nice intro. It shows the language features followed by some code examples, sweet, thanks for the link!

Re: Elixir v0.5.0 released

#8
post #4

Is it me or a release notes with a list of what changed is nowhere to be found?

Consider this the initial release. The previous alpha versions were designed completely different, so release notes don't apply for this release. We will maintain a CHANGELOG from now on: https://github.com/elixir-lang/elixir/blob/master/CHANGELOG....

Re: Elixir v0.5.0 released

#10
I used to be very excited about Elixir, not because I hate Erlang's syntax (I actually quite like it), but because I saw in it the opportunity for a mainstream, general purpose language with macros on top of the excellent Erlang runtime.

However, after 2 small projects with Clojure, my thoughts have changed. To me it is the general programming language, and it's only a matter of time until clojure-beam sees the light of day (there's already Joxa).

Also, it occupies a weird spot: after v0.4's redesign, it pretty much kept Erlang's semantics, which made it unlikely to be adopted by old Erlangers and, with the whole OO thing was thrown away, it is too much a departure from Ruby.

Post reply on HN