Ffs jutty, that was confidential! What a man does in the privacy of his own garden is his business alone. And anyway, there’s nothing unusual about wanting to bathe in a giant margarine pit. Don’t make it weird.

This is a helpful resource for finding European alternatives: european-alternatives.eu/category/fil...

I grew up in them there parts. The Old Smithy is a great spot for a pint in you’re up near the coast. Have fun counting trees!

Congratulations Angie! What a journey it’s been.

The dream combo.

😂 🧼

Same! However, you *can* do progressive enhancement with D*, as we both found out (even if it annoys the author!). And overall, it’s a more flexible framework with much better ergonomics, I think. So I’m going to keep a foot in both camps :)

I think this you’ve hit on a key philosophical distinction - htmx encourages progressive enhancement, D* emphasises real-time hypermedia. Both are valid approaches.

Sprig / htmx has history support baked in (including caching and scroll position restoration) so if it’s an important part of your multi-faceted search interface then it’s still a better choice, imo.

Interesting article! I created something similar with Ben’s early version of Datastar for Craft (‘Spark’), and ended up creating a web component to manage history state: github.com/putyourlight...

I got push back from the D* dev about the history api, but he later changed his mind somewhat.

I remember your fabulous hair! Good times.