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

Here's what the latest issue looks like:

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

Surface and Phoenix LiveView - What Comes Next?
Marlus wrote about LiveView's new template engine called HEEx (HTML+EEx) and the path to bring Surface's features and components into LiveView.

Elixir v1.12 released
There is some really neat stuff in this release: `Mix.install/2`, OTP 24 integration, better errors and much more!

Using Oban to License Oban
Peek behind the scenes to see how Soren uses Oban to demo, license, and actively verify Oban Web+Pro.

Building Morsecipher
Aidan build a morse code translator. Pretty cool.

Even more from around the Elixir community

Elixir Outlaws: I'm Here to Tear It all Down Podcast

Elixir Wizards: The Right Amount of Magic with Erik Person Podcast

Thinking Elixir: Ecto Associations with Sheharyar Naseer Podcast

Elixir Wizards |> Conference Conference

Interfacing Elixir with Ruby or Python Through ExPort (erlport) Blog post

Let's Build An Instagram Clone With The PETAL Stack [part 5] Blog post

Let's Build An Instagram Clone With The PETAL Stack [part 6] Blog post

Ecto.Repo.stream/1 in Large Data Processing Blog post

How to Split a Router into Multiple Modules Using Phoenix Blog post

Efficiently Querying Data in Batches with Absinthe Blog post

Database Modeling With Ecto Part 2 Blog post

Introduction to Elixir (part 1) Blog post

Debugging and Mocking Third Party Services in Elixir with Mox Blog post

Intro to Processing Log File with Elixir Blog post

fremantle-industries/notified_phoenix 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 :)


Feedback? Questions? Anything else?

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