Live data from Hacker News

Erlang/OTP 18.0 has been released

erlang.org

31–40 of 42 posts

Re: Erlang/OTP 18.0 has been released

#31

Earlier quoted context omitted.

See, this would not have happened if they had coded this project in a purely functional language.

It would not have happened if that logic was covered by tests :O

Yes and no. Erlang/OTP has a pretty extensive test suite which takes several hours to run. There is a nightly test run on a multitide of architectures. So it is some times the case that a fault is caught at night and fixed the following day.

The Erlang/OTP team runs a mantra where everything is covered by tests and they are doing a really good job at what they are doing. So I would not be surprised to see this having been caught by a test.

Re: Erlang/OTP 18.0 has been released

#33
post #16

Earlier quoted context omitted.

Random numbers (18 vs Python's 3 or Java's 8) don't mean anything without comparing the release cycles and version numbering schemes as well. I could make small incremental updates to a toy language and release them every week to get to FooBarLang 200.0.0, that doesn't mean it's progressing faster than a language at release 2 or 10.

That's the joke.

Maybe add the /s then?

It's amazing how many people actually confuse version numbers this way, including on HN (check any discussion about semver).

Re: Erlang/OTP 18.0 has been released

#34
post #9

For the first time Erlang 18 shipped under Apache License 2.0, it will likely have a meaning for Erlang's future development. The Industrial Erlang User Group has spent quite some effort on that.

Can you explain why, or link to a summary of the history? Wasn't it a license specific to erlang in the past? If so that's great as Apache is standard. But if it went from another common license I'm curious to know why.

Re: Erlang/OTP 18.0 has been released

#35
post #11

Something you may find interesting is that the new faster maps are loosely based on Rich Hickey's HAMT implementation that is used in Clojure. Jose and co. in Elixir adapted/is-adapting their internals to use maps as well, as they were faster than any implementation they had. In addition, I wrote a full QuickCheck model for the new maps. That is, we randomly generate unit test cases for the maps and verify them. We h…

Some great articles about the process of "Breaking Erlang Maps" via QuickCheck. Thanks for those!

1: https://medium.com/@jlouis666/breaking-erlang-maps-1-31952b8...

2: https://medium.com/@jlouis666/breaking-erlang-maps-2-362730a...

Re: Erlang/OTP 18.0 has been released

#36

Commits like this make me realize, "oh, they're just developers like me" https://github.com/erlang/otp/commit/37f143e9e16e89d753b0e5e...

See, this would not have happened if they had coded this project in a purely functional language.

Exactly, because if it was a purely functional language, they would have started the project, worked on it for a week, blog about it and said purely functional language for a year, then throw it away.

Re: Erlang/OTP 18.0 has been released

#37
post #34
post #9

For the first time Erlang 18 shipped under Apache License 2.0, it will likely have a meaning for Erlang's future development. The Industrial Erlang User Group has spent quite some effort on that.

Can you explain why, or link to a summary of the history? Wasn't it a license specific to erlang in the past? If so that's great as Apache is standard. But if it went from another common license I'm curious to know why.

It didn't come from another common license. It came from the EPL (Erlang Public License http://www.erlang.org/EPLICENSE). Erlang users have been asking for the change for years and OTP 18 finally delivered on the promise.

Re: Erlang/OTP 18.0 has been released

#38
post #34
post #9

For the first time Erlang 18 shipped under Apache License 2.0, it will likely have a meaning for Erlang's future development. The Industrial Erlang User Group has spent quite some effort on that.

Can you explain why, or link to a summary of the history? Wasn't it a license specific to erlang in the past? If so that's great as Apache is standard. But if it went from another common license I'm curious to know why.

The previous versions of Erlang were using the Erlang Public License 1.1, a modified Mozilla Public License adapted with Swedish laws. https://en.wikipedia.org/wiki/Erlang_Public_License

Re: Erlang/OTP 18.0 has been released

#40
post #13

The improved time handling is the biggest new feature for most users probably (apart form maps improvements and the new license). http://www.erlang.org/doc/apps/erts/time_correction.html

Fred Hebert, author of Learn You Some Erlang has a new postscript to the book about the new way time will be handled in Erlang 18+ :

http://learnyousomeerlang.com/time

(BTW, there's also a talk from Erlang Factory by Lukas Larsson on the subject:

https://www.youtube.com/watch?v=gfsc2MyP8p8&list=PLWbHc_FXPo... )

Post reply on HN