ElixirWeekly

Issue #240 - Nx is now Publicly Available

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

Here's what the latest issue looks like:

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

Cursed Curried Elixir
Although you love currying and think macros are cool, remember the first rule of meta-programming while reading this.

Nx is now Publicly Available
José's announcement post for Numerical Elixir and the Nx project.

Elixir Now #48 in TIOBE Index
Elixir made it into the "Top 50 Languages" this year! While the methodology can be called into question, Elixir is now "officially" outranking some traditional languages in terms of meaningless internet points.

Even more from around the Elixir community

Thinking Elixir: X-Plane's Elixir MMO with Tyler Young Podcast

Elixir Wizards: Yair Flicker on SmartLogic’s Origin, Evolution, and Elixir Adoption Process Podcast

Elixir Berlin Meetup February 2021 Video

Handling Configuration Variables in Elixir Blog post

OpenTelemetry Specification v1.0.0, Tracing Edition Blog post

Conditional Guard for Structs of an Explicit Type Blog post

Conditional Context for Macros Blog post

Building a Real-time Kanban Board with Phoenix LiveView Blog post

Building an Event-sourced Game with Phoenix Liveview: Game Server Blog post

Database Session Store with Elixir and Plug Blog post

Introducing Elixir Buildpack Blog post

The Case of the Red Bug Blog post

pawurb/ecto_psql_extras Project update

KronicDeth/intellij-elixir Project update

Noozo/website 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).