ElixirWeekly

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

Here's what the latest issue looks like:

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

fast_html
fast_html is a C-Node which wraps the Myhtml library, replacing HtmlSanitizeEx at Pleroma after 2 years of great service, because people were submitting multi-megabyte posts which HtmlSanitizeEx has had problems handling.

Highlights from the Big Elixir 2019
The fine folks of SmartLogic had a great time at the Big Elixir – check out their recap for highlights on some of their favorite talks and moments from the conference.

Broadway, RabbitMQ, and the Rise of Elixir Part 1
In this blog post, Alex covers how to setup RabbitMQ along side Broadway to create a powerful yet simple data processing pipeline.

Caching with Elixir and ETS
Get started using ETS as a caching mechanism in your Elixir applications and pick up some useful tips and tricks.

Reading 13F SEC Filings With Elixir - Part 1
This sounds a bit boring, but it's a great read! ^_^

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