ElixirWeekly

Issue #186 - Lumen - Elixir & Erlang in the Browser

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

Here's what the latest issue looks like:

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

Elixir v1.10 Released
Elixir v1.10 comes with improvements to the standard library, the compiler, as well as several additions to the mix release feature added in v1.9.

Lumen - Elixir & Erlang in the Browser
Lars' thoughts on Lumen and a guide to trying the current bleeding-edge development version yourself. Where you can write Erlang or Elixir to run in your browser.

Six Famous Companies Using Elixir - And Why They Made the Switch
Some big companies switched to Elixir because of its scalability and reliability. Articles like this are great to educate business people as well. And this is the best kind of stuff to help with adoption.

Cool Elixir Libraries
A list of ... well ... cool Elixir libraries. :)

Periodic Jobs in Elixir with Periodic
One cool thing about BEAM languages is that we can implement periodic jobs without using external tools, such as cron. In this article Saša presents his own abstraction called Periodic.

A Proposal for an Absinthe Application Structure
Devon came up with a project structure that he likes for Absinthe applications, and he took the time to write it up!

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 :)

Contact

Feedback? Questions? Anything else?

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