Issue #129 - Expecting the Unexpected
Every Thursday: No frills, no click-through, no spam.
Here's what the latest issue looks like:
This week in Elixir
Elixir v1.8.0-rc.0 released
The Elixir Core Team released the first release candidate for Elixir v1.8.0. For more information, checkout the CHANGELOG.
Expecting the Unexpected
Distributed transactions have some pitfalls, particularly when relying on network requests which may fail. The fine folks at Qixxit wrote up an approach to handle these in Elixir, using the example of capturing payments through a 3rd party.
ElixirOutlaws is looking for your support!
If you are enjoying the show please consider helping them offset the costs by pledging to their Patreon!
WaspVM - A WebAssembly Virtual Machine
The team at Elixium Network has been working on a WebAssembly virtual machine that runs on Elixir. Although they’ll be using it internally in the Elixium blockchain, WaspVM is built to be general-purpose.
How to manage Elixir versions on Mac or Linux
Getting started with Elixir can be a bit of a struggle… what Elixir versions do you need to use? What Erlang versions are compatible? How does one switch between them? This guide has you covered!
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).