ElixirWeekly

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

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #426

Welcome to Issue #426

Hi there,

this issue is a bit late due to some work related travel.

This week in Elixir

Elixir Macros Demystified: Defmacro and Require
George wrote this post about defining macros using defmacro, handling and returning quoted expressions, and why you need to ‘require’ macros before using them.

Putting a full power search engine in Ecto
Cameron explored what it takes to support ParadeDB in Ecto, essentially providing a full text search enging in PostGres database.

LiveView Native In The Wild
Brian wrote about what people are building with LiveView Native.

Even more from around the Elixir community

Elixir Friends: Episode #1 Podcast

Thinking Elixir: From Keynotes to Job Listings Podcast

All Videos from Code BEAM Lite Mexico Video

How to find the 🐢 slowest N modules in test suite Video

Note: Alias for fast testing in Elixir Blog post

Data Channels in Elixir WebRTC Blog post

Testing in Elixir and LiveView Blog post

Create Your First LiveView Native App - Part 1 Misc

What Happens when you Type a Phoenix URL into Your Address bar and Press “enter”? Blog post

Exciting Updates to phx.tools Blog post

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