ElixirWeekly
Issue #17: Beyond 10,000 Lines of Elixir, String Manipulation Micro Optimisation and Distributed Supervisors
Every Thursday: No frills, no click-through, no spam.
Here's what the latest issue looks like:
This week in Elixir
Beyond 10,000 Lines
Daniel from Infinite Red wrote a blog post about lessons learned from building a large Phoenix project (> 20,000 lines).
String manipulation micro optimisation using IO lists
This blog post demonstrates a real-world example of swapping naive string manipulation for an IO list. The benchmarked gains for the affected use case were a 20 - 25% performance improvement.
Pluralsight Course: Getting Started with Elixir
This course by Nate goes over the basics of data types, functions, recursion, iex, and mix. It concludes by creating a supervisor application to send out Tweets using ExTwitter.
Ecto.Rut v1.2.0 released
Ecto.Rut provides you with simple shortcut methods to perform Ecto operations (without calling YourApp.Repo or concerning yourself with changesets everytime).
Distributed Supervisor test
This is a small experiment by Ricardo to test out a system where we have multiple nodes and a single worker process, registered globally, and running a task every two seconds.
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).
