Some more things about Django I've been enjoying

A programmer’s cheerful post about learning to build websites the old-school way — with pages made on the server and a database doing the heavy lifting — somehow turned into a mini culture war in the comments. The author is basically saying: “I tried the modern, frontend-heavy route, got tired, and now I’m weirdly enjoying Django,” a long-running Python web tool that helps people build sites without drowning in browser code. They rave about how readable it feels, how handy its built-in page helpers are, and how magical it is to change data models and get automatic database updates.

And the community? Oh, they had feelings. One camp showed up like loyal sports fans, calling Django the one framework that still “scratches the itch,” with one longtime user saying they’ve stuck with it since version 0.95 and still use it even when the rest of the company runs on other languages. Another commenter practically crowned Django’s database and migration system king.

But then came the backlash. One critic declared Django’s filter style is like “fingernails on a chalkboard,” which is exactly the kind of dramatic phrasing the internet was built for. And the Go fans were not about to let a Python lovefest go unchallenged: one bragged their Go app serves around 100 requests per second and accused Django of wasting memory. Meanwhile, a separate performance note lit up the practical crowd: turning on template caching reportedly boosted the site from 2–3 requests per second to around 12, which commenters treated like both a win and a roast. In other words: wholesome coding diary on top, framework fandom cage match underneath.