ElixirWeekly

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

Here's what the latest issue looks like:

Issue #264

This week in Elixir

A Gentle Introduction to Machine Learning for Developers
Benjamin blogged about learning the basics and getting started with Nx and Axon from first principles.

What If ... CobolToElixir
Mike draws parallels between the Marvel Cinematic Universe and Elixir community as he asks: “What if we could transpile COBOL into Elixir?”

EFLFE: Elixir Flavoured Lisp Flavoured Erlang
Mariano on how a literal joke turned into an interesting project.

Why we Killed Elixir
Borislav writes about why his team ditched Elixir in favor of Go. In my opinion it is important for us as a community to have these discussions rather than avoid them (in this case, Elixir seems to have been a bad fit for the team IMHO).

Even more from around the Elixir community

Elixir Outlaws: The Gardening Outlaws Podcast

Thinking Elixir: How Elixir Came to Spotify with Joel Kemp Podcast

Elixir Wizards: The Bridge Between Elixir and Zig with Isaac Yonemoto Podcast

Elixir Wizards: Delving Deeper into Magic with Quinn Wilton Podcast

Let the Force be with Livebook Blog post

Mixing Clean Architecture Blog post

Protocols vs. Behaviours in Elixir: Additional Thoughts Blog post

Using Tree Structures with Pagination to Build Folder Navigation Blog post

phx.new Webapp Project update

fremantle-industries/history: Download and Warehouse Historical Trading Data 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).

ElixirWeekly by @elixirstatus

ElixirWeekly

Questions & Answers

Contact