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.<p>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 have generated several millions of those test cases, including variants which heavily collides on the hash. This weeded out at least 10 grave bugs from the implementation, which in turn means this release is probably very stable with respect to maps.
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.
Commits like this make me realize, "oh, they're just developers like me"<p><a href="https://github.com/erlang/otp/commit/37f143e9e16e89d753b0e5e4415968dbcd5f6b65" rel="nofollow">https://github.com/erlang/otp/commit/37f143e9e16e89d753b0e5e...</a>
The improved time handling is the biggest new feature for most users probably (apart form maps improvements and the new license).<p><a href="http://www.erlang.org/doc/apps/erts/time_correction.html" rel="nofollow">http://www.erlang.org/doc/apps/erts/time_correction.html</a>
I love Erlang releases and am very happy about the improvements to maps. I have to admit the OTP motto of "move slow and never break anything" always leaves me wanting more (though).
> ssl: Remove default support for SSL-3.0 and added padding check for TLS-1.0 due to the Poodle vulnerability.<p>> ssl: Remove default support for RC4 cipher suites, as they are consider too weak.<p>I'm not following Erlang news but was just wondering, aren't these fixes coming out way too late?