3 ms·

This feels right and wrong at the same time. It’s right (as explained in the about): - to like Django and all the 1000s of contributions - to be frustrated b

This feels right and wrong at the same time. It’s right (as explained in the about): - to like Django and all the 1000s of contributions - to be frustrated by its limits & to want to do more - to fork and rearchitect if you can’t get there by debate - that people may like it and come along or the ride - in many of the features and design points - to embrace HTMX It’s wrong: - to try to innovate on the Python/Django ecosystem - to miss out on functional code for HTML composition - to continue the framework paradigm - HTMX leads to server side which leads to devs reclaiming the application loop If, like me, you feel that plain is on the right track, but want to go faster / further, then I encourage you to take a look at https://harcstack.org https://harcstack.org. [disclaimer, I am the author]

barrenko 2y ago
Do you have more posts about this? My main gripe about Django is that the usual html templating options are but-uggly (as opposed to those that ship with Rails), but I haven't tried one of the new options.
- librasteve 2y ago
  thanks for your interest … I have this to whet you appetite https://rakujourney.wordpress.com/2024/10/27/raku-htmlfunctional/ https://rakujourney.wordpress.com/2024/10/27/raku-htmlfuncti... i’m planning a series of posts on HARC stack starting tomorrow (just finalizing first one) you can use the RSS at https://raku.org https://raku.org or subscribe to https://rakudoweekly.blog/ https://rakudoweekly.blog/ to get them
- m000 2y ago
  I wish django's template engine was demoted to a contrib package and eventually replaced by jinja (i.e. jinja becoming a django dependency). I understand that django templates started with the intention of eliminating programing logic in the templates (presentation). But the implementation of the concept is very puritanistic, to the point of becoming counter-productive. Jinja's approach OTOH is less opinionated: you can be a puritan and emulate django's approach if you want, but you can also be less dogmatic about the logic/presentation separation if that serves you. As someone very aptly put it on reddit [1]: > Jinja may let program logic layer bleed into the presentation layer, but with Django it seems there's no way to do it without presentation layer bleeding into program logic layer. [1] https://www.reddit.com/r/django/comments/13n9pfd/is_it_me_or_django_templates_suck/ https://www.reddit.com/r/django/comments/13n9pfd/is_it_me_or...
BoorishBears 2y ago
And immediate and persistent 502 is not a great endorsement.
- librasteve 2y ago
  eating own dog food and I made an error - red face

barrenko 2y ago

Do you have more posts about this? My main gripe about Django is that the usual html templating options are but-uggly (as opposed to those that ship with Rails), but I haven't tried one of the new options.

librasteve 2y ago
thanks for your interest … I have this to whet you appetite https://rakujourney.wordpress.com/2024/10/27/raku-htmlfunctional/ https://rakujourney.wordpress.com/2024/10/27/raku-htmlfuncti... i’m planning a series of posts on HARC stack starting tomorrow (just finalizing first one) you can use the RSS at https://raku.org https://raku.org or subscribe to https://rakudoweekly.blog/ https://rakudoweekly.blog/ to get them
m000 2y ago
I wish django's template engine was demoted to a contrib package and eventually replaced by jinja (i.e. jinja becoming a django dependency). I understand that django templates started with the intention of eliminating programing logic in the templates (presentation). But the implementation of the concept is very puritanistic, to the point of becoming counter-productive. Jinja's approach OTOH is less opinionated: you can be a puritan and emulate django's approach if you want, but you can also be less dogmatic about the logic/presentation separation if that serves you. As someone very aptly put it on reddit [1]: > Jinja may let program logic layer bleed into the presentation layer, but with Django it seems there's no way to do it without presentation layer bleeding into program logic layer. [1] https://www.reddit.com/r/django/comments/13n9pfd/is_it_me_or_django_templates_suck/ https://www.reddit.com/r/django/comments/13n9pfd/is_it_me_or...

BoorishBears 2y ago

And immediate and persistent 502 is not a great endorsement.

librasteve 2y ago
eating own dog food and I made an error - red face