having something that specific, tailored for dynamic language, seems like overkill
i'd undestand if it was for something highly performant and hard to deploy
I honestly liked the website more than the extension.
And disliked the promotion of having productuhunt before the brand.
For the same purpose, I already use kill sticky headers.
> Usually this can be resolved by creating a new function and calling that from the loop. But frequently not. [etc.]
For me this is the appeal of the language; I really prefer things confined and manually scoped rather than having things globally scoped which would cause a lot of debate just around that. You often have to think about what you want to expose and where, but that's a good thing in my opinion.
I have airconnect on a raspberrypi so I don't have to keep my laptop on and I can play songs from my iphone that way, just stream to chromecast audio. It's also worth mentioning it works a bit better than mkchromecast but it depends on your wifi.
- part 2: https://www.mostlypython.com/django-from-first-principles-pa...
- part 3: https://www.mostlypython.com/django-from-first-principles-pa...
also here's the repo: https://github.com/ehmatthes/django-first-principles/