So Django did not fit the author’s use case of implementing endless scrolling? How is Next better at this? Are there use cases where one could be suited more than the other, before we completely start writing off everything else?
1) it doesn't matter that you know Python. If you want to get good with Django you have to know Django;
2) documentation is so technical it's mostly useless for the casual user googling for issues;
3) templating DSL starts to get messy as you grow. There's no official or de-facto linters, formatters so you're left using someones hobby project. Suppose if you spend time customizing it, it works, but no where near what prettier and jsx as a whole bring;
4) I want my web pages to behave modern, so in Django terms that means Django + htmx + alpinejs. Have fun figuring everything out yourself because while there's resources for these individually, there's barely anything for combined usage. Yes they're tech agnostic but as I started building with them, I had no idea how not to make it messy.
My take is that you should use Django if you're already fluent in Django or you're hellbent on sticking with Python. In my case it boiled down to this -
1) learn django, htmx, alpinejs, settle for simpler template tooling;
2) use python backend and js frontend;
3) rip the bandaid, learn js and do web the modern way;
I found 3 to be most appealing as it keeps everything under the same ecosystem. There are cons ofcourse, i.e. amount of dependencies, frameworks come and go, but my dev experience has been pleasant, issues easy to google, official docs useful.
