django-unicorn

I wrote the third blog post in a series about django-unicorn. This one was focused on how the reasons that the project was created, Python and JavaScript libraries used.

Every time I write a post I marvel at how long it takes, but I do think it's worthwhile in the long run to get the word out about django-unicorn and hopefully people find it interesting.

On a lark, I set up GitHub sponsors for django-unicorn and to my surprise, someone signed up! It almost pays for the monthly server bills to host the documentation site. :)

It has been a great motivator to see that someone believes in the project and we've even gone back and forth on Twitter and GitHub to talk about certain aspects of the code.

I really appreciate how easy GitHub made that functionality and excited for what's to come.

After watching the available Livewire screencasts I really wanted to at least prototype a project with it. But... not enough to switch away from my typical tech stack of Python and Django. Laravel looks nice, but I am pretty invested in the Python ecosystem. So, I tweeted complaining that Django didn't have a similar library and my friend, Michele, then replied with the magic question: "why don't you make it yourself".

I spent the next 3 days re-watching the Livewire screencasts pretty intently to see the "shape" of the JSON request and response messages, scouring the documentation site, and reading through the Livewire Javascript code to understand how it worked. My first push to Github was July 11th -- three days after that first tweet.