Live data from Hacker News

Elixir 1.9

elixir-lang.org

1–10 of 174 posts

Re: Elixir 1.9

#2
quite new to elixir ( still haven't deployed anything to prod ).

interested to know, how the releases feture going to affect the way we deploy elixir/phonenix apps in production ?

Re: Elixir 1.9

#4
This is great news! The deployment story has progressively improved since I started using Elixir in 2016, but the best way is to just have _one_ community blessed system.

Distillery has helped a lot for sure, so it's nice that it's basically been rolled into the base elixir distro.

Re: Elixir 1.9

#5
Fantastic. Congratulations to the Elixir team!

Something striking from the release announcement:

> As mentioned earlier, releases was the last planned feature for Elixir. We don’t have any major user-facing feature in the works nor planned.

Part of me is a little alarmed—no one wants a language to stagnate. José makes it clear that this doesn't mean it's the last version:

> Of course, it does not mean that v1.9 is the last Elixir version. We will continue releasing shipping new releases every 6 months with enhancements, bug fixes and improvements.

Elixir is remarkably extensible. When I was first getting acquainted with the language finding macros with all the expressive ability of a LISP blew my mind. Making powerful macros a core part of the language meant that the language could grow. That in my mind is the most important part of any language's long-term viability.

Fantastic work all who contributed. Thank you for making a fast, functional, and fun language to work with!

Re: Elixir 1.9

#6
Sorry if this is a dumb question, but how do releases fit into the deployment story with containers so prevalent these days? (As in why is this a benefit when you can just package code into a single container to ship it?) Is it that it works with hot code updates? Or it’s a more Erlang-sanctioned way of deploying code?

Re: Elixir 1.9

#7
post #4

This is great news! The deployment story has progressively improved since I started using Elixir in 2016, but the best way is to just have _one_ community blessed system. Distillery has helped a lot for sure, so it's nice that it's basically been rolled into the base elixir distro.

Based on what I've learned from the Elixir forum, these new releases have "no support for hot code updates / appups / relups".

This means that Distillery will remain the best choice for many of us, including myself.

I have a very simple deploy process with Edeliver and Gitlab CI/CD that basically just consists of pushing or merging a commit to master that passes the tests. There's zero down-time and it doesn't require containers on the server.

I'd also say that the "deployment story" wasn't any worse than Rails or other stacks in the past except in that people have a choice of having a stateful server.

This is how I'm doing it now: https://youtu.be/-mm44ADU3kc?t=172

Re: Elixir 1.9

#8
post #2

quite new to elixir ( still haven't deployed anything to prod ). interested to know, how the releases feture going to affect the way we deploy elixir/phonenix apps in production ?

Previously most people used distillery. Now they'll use Elixir releases. Because it is pretty much the same solution but now moved into the language tooling itself.

Re: Elixir 1.9

#9
post #3

Are releases supposed to replace Distillery? If so, are there any particular reasons to switch?

I guess so, I imagine that's up to the maintainer.

Re: Elixir 1.9

#10
post #2

quite new to elixir ( still haven't deployed anything to prod ). interested to know, how the releases feture going to affect the way we deploy elixir/phonenix apps in production ?

You can simply "mix release" to build a release without using the Distillery library. There are some limitations, though, mentioned on the forums: https://elixirforum.com/t/elixir-v1-9-0-released/23366/4
Post reply on HN