But also to basically decide that the language ergonomics and syntax is "finished" this quickly is truly impressive. The addition of macros, combined with the huge focus on developer experience, I think allows the core team to say "its feature complete" while not worrying about any particular missing features in the language (you can probably just implement it yourself anyway)
José Valim was the one who added "Add {continue, Term} and handle_continue/2 to gen_server" - https://github.com/erlang/otp/commit/69e009e3e1ad899a4609ff3...
José's contributions are at https://github.com/erlang/otp/commits?author=josevalim and Michał Muskała's at https://github.com/erlang/otp/commits?author=michalmuskala - there may be other Elixir devs in https://github.com/erlang/otp/graphs/contributors. (I even got in a tiny optimization myself once: https://github.com/erlang/otp/commit/07b0f4315b079cce7aeef7b...)
This is also an area where Elixir is benefiting greatly from the maturity and ongoing development of the Erlang VM. Elixir is, in a sense, simply a text based interface on top of the BEAM.
This isn't directed specifically at you, but to anyone who might have ideas.
For example, they recently scrapped plans on building property testing into the language core.
Which is something I find very refreshing, TBH, having worked with the JS ecosystem, I somehow find this approach to be rather relieving for some reason.
> There is only one last major feature planned for upcoming Elixir versions, which is the addition of mix release to Elixir itself, streamlining the experience provided by packages like distillery.
Aside from having native support for releases, which would be killer, I was really struck by the idea that the language will be basically "finished". You rarely see that in software these days, but I think there's a lot to be said for trying to get to that point.