ElixirWeekly

Issue #166 - How to Create Desktop Applications with Elixir

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

Here's what the latest issue looks like:

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

Hex Diff
Johanna created an online Hex package diffing tool. Just put in a package name (try 'credo') and it will show you the latest changes.

How to Create Desktop Applications with Elixir
I thought the title was clickbait, but this seems to be a valid proof-of-concept (link to source on GitHub included).

Elixir Performance – Using IO Data Lists
Eric was inspired to work on some of my side projects to make them use IO lists instead of plain strings after watching Johanna's ElixirConf 2019 talk "High Performance String Processing Scripts in Elixir".

Deploying Phoenix to Kubernetes from Scratch
A complete guide to deploying a Phoenix application to a new and empty Kubernetes cluster.

jayjun/rambo
Rambo has one mission: Start your program, pipe standard input, send EOF and return with output.

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