Every Thursday: No frills, no click-through, no spam.
Here's what the latest issue looks like:
This week in Elixir
Waiting for an Answer
Snorri, who's day job is working on EVE Online, describes his first iteration of `exsim`, the core server for a large scale space simulation written in Elixir, Go and C++.
Ricardo created this small tool for assisting you while developing or testing Phoenix sockets and channels, or in other words, a minified version of the famous Postman app but for Phoenix WebSockets.
Phoenix WebSockets Under a Microscope
This is a code-reading and exploration by Dimitris about the WebSockets side of Phoenix. It builds upon tracing techniques to observe some of the internals of Phoenix.
Automatic Bang! Function Generation in Elixir
Isaac just published `unsafe` which aids in the generation of bang functions based on easy module attributes.
A Short Overview of Elixir Executables with escripts
This is a short intro by Roberto to escripts, what they are, how they integrate with mix and why you should avoid using archives.
How to Automatically run Stale Tests on File Change in Elixir
Andrew wrote a short article with scripts to automatically run stale tests whenever a file is changed.
On Making The Future
This is a nice blog post by Desmond on the philosophy behind the creation of Empex, an NY Elixir conference which just an LA counterpart.
Elixir with Love
Here’s Robert's short recap from the Elixir with Love conference last week. With a mix of great talks about technology and community, it got him excited about the future of Elixir.
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).