ElixirWeekly

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

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #279

This week in Elixir

Launching Livebook Using LiveView
Mark writes about creating fly.io‘s Livebook launcher in LiveView!

Writing a Genetic Algorithm in Nx
Sean wrote about writing a Genetic Algorithm that can run on a GPU with Nx and EXLA.

A Nice Dashboard UI
Intro into how to create a nice looking LiveView dashboard by Alvise.

Debugging Elixir Phoenix: Beyond IO.inspect/2
Jack covers some options for debugging Elixir when using IO.inspect/2.

Even more from around the Elixir community

TIL: Elixir IEX Multi-line Command Misc

Thinking Elixir: New to Dev or Elixir and Women in Tech with Miki and Kate Rezentes Podcast

Elixir Wizards: The Benefits of Consistently Growing Your Toolset with Florian Kraft Podcast

Build a Postgres Proxy in Elixir Using Pattern Matching Blog post

Expectations with Mox Blog post

Safe Ecto Migrations Blog post

Building a Simple Calendly Clone with Phoenix LiveView (pt. 3) Blog post

One way to Handle Static Asset Files in Phoenix 1.6 Blog post

Deploying Elixir Ebook Blog post

alexiob/forthvm: Forth VM/Interpreter Written in Elixir Project update

artur-Sulej/excellent_migrations: An Elixir Tool for Checking Safety of Database Migrations. Project update

Submit your blog post/project update

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