Every Thursday: No frills, no click-through, no spam.

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #114
This week in Elixir

Introduced at ElixirConf: NervesHub helps you manage firmware updates for Nerves devices!

Wrapping Up ElixirConf 2018
Joshua wrote up his thoughts on Elixir and ElixirConf 2018.

[VIDEO] Introducing Scenic, A Functional UI Framework
This video is a MUST-watch, showing Boyd's work on Scenic, a fully functional 2D graphics framework for Elixir powered by OpenGL!

Using Facades to Simplify Elixir Modules
Let’s dive into how Pete has been using the "facade" pattern to simplify and shorten his Elixir modules.

Introducing Squabble, Simple Leadership Election
As part of his ElixirConf talk, Eric showed off Squabble, his new Elixir package for selecting a leader in your cluster.

Phoenix’s LiveView: Client-Side Elixir At Last?
A quick rundown of the new LiveView feature for Phoenix announced by Chris McCord at last week's ElixirConf.

Why Phoenix.LiveView is a big deal
Derrick believes Phoenix.LiveView has the potential to reshape the way many developers build reactive user interfaces on the web. Here’s why.

SpawnFest 2018 is here!
An annual 48 hour free online development competition in which teams of skilled developers from around the world get exactly one weekend (Nov 24/25) to create the best BEAM-based applications they can!

That's it for this round, have a great day!
@rrrene from ElixirWeekly

If you like this newsletter, please tell the world!

You can view this issue in your web browser.

You can subscribe below:

Questions & Answers

Can I submit things I made to be included in the next issue?

Yes! Simply post them to ElixirStatus and you can be sure that they land on my radar.

Is my email address safe with you?

Yes. I'd like to consider myself a trustworthy individual, but then who doesn't?

I am, however, an active member of the open-source Elixir community and the maintainer of Credo and ElixirStatus. I will NOT ruin my reputation by selling your data to a third party.

Why do you require me to confirm my email address?

I just believe that requiring double opt-in to subscribe to any email-based system is a win for both parties: You are safe from unintentionally subscribing and I can be confident that you actually own the email address and want to receive the newsletter I send you :)


Feedback? Questions? Anything else?

Please contact René Föhring (email or tweet @rrrene for a quick conversation).