is this useful w/ htmx? Well, kinda. But you can also avoid it if you want. Which is better?

The way I see it, HTMX and hyperscript already provide a brilliant, low-maintenance and super high-level solution to the frontend - without necessarily focusing on how the backend is implemented. As @User pointed out, this may make it a bit more challenging to show some concrete examples in the docs, but I'm sure we can pull our heads together and work on it! 😉

I'm also suggesting that the docs gain some more advanced examples because I've seen 1cg answer the same sort of question multiple times, and it comes down to that disconnect on where to draw the line between the frontend and backend.

unrelated but I think I remember my dad talking about this pattern when I was a kid like years ago lol

sometimes I forget just how long some folks have been doing web development lol

Was this the channel where I was talking about my COBOL days, or was that somewhere else? LOL

Y2K happened before I was born, yet I'm hold enough to have this conversation with you 😅

we're all gonna make it frens

Like this, but with less smiling...

in conclusion, javascript is wrong

Shoot. It was fun, using XML and XSLT to make the greenbar-printer-printing, formerly-punch-card-input-taking magical box in the building across the street - put out a really cool web page!

I think I scared him, he's fallen back to the only thing he remembers!

XSLT - I wonder how many people even know what that is anymore...

at first glance I thought it was once of the excel formats

At least people know COBOL, at least by name...

LOL

after looking it up, it seems much more cursed (transforming XML schemas to other XML schemas? They made a language for that!?)

@User remembers. It's why

@foo

means "attribute foo" in hyperscript

Think of it as stylesheets for bare XML files. You could take an XML and an XSLT, and use it to transform one into the other. Within browsers, if you generated a link to an XSLT file within the XML, the browser would do that transformation. So, what I did in that particular case was to write a nice web page frame around the expected data, then the COBOL returned the XML with the link (very early "API call" - LOL). It was kinda cool, but what made it really cool was that it was output from a mainframe. "YOU CAN DO THAT?!?!?!" "Well, yeah, if you don't just sit around and grouse about how old COBOL is..."

@User Perhaps it would be nice to have some generic best practices and patterns to common use cases where you don't go too deep into detail about the server but enough so that the developer can grok what is necessary to implement. I love the examples you have on the site but then I am left to asking questions here that I know there is an easy answer just waiting to happen.....

we could probably stand a "Server Side Patterns" page

but then I'd need to know what the best server side patterns are, and I'm just here for the memes

😑

I am happy to help out on the Django side of things as far as communicating how things should/could work.....

I know I struggled with P/R/G, but the biggest gotcha I encountered was that the AJAX request followed the redirect before returning. I ended up designing around that, but I'm guessing there's a better way?

@User I'd be happy to help setup a 'playground' using Kirby - i.e., a Kirby site that would respond with sample data, suitable for testing/playing with HTMX. I'd be happy to move the current HTMX+hyperscript sites to Kirby - and provide hosting. If it would be interesting to the team, let me know. 🙂