bencroker.com
Craft CMS plugin developer, builder of shiny tools;
modern day drifter, adventurous fool.
27 posts
145 followers
38 following
Regular Contributor
Conversation Starter
comment in response to
post
Dub, for dubdubdub (www)?
comment in response to
post
Learn the chords for a song he loves. “Somewhere Over the Rainbow/What a Wonderful World” by IZ was that song for me on the ukulele.
youtu.be/V1bFr2SWP1I
comment in response to
post
I was going to suggest using SSE responses but, having looked at the source code, I see that you have no backend, just an SPA that fetches JSON from an API endpoint. There’s too much heavy lifting going on in the frontend for my liking, but cool to see how Datastar is driving frontend reactivity.
comment in response to
post
They’re completely different approaches – you choose what you’re more comfortable with. Sprig is component-based and provides backend reactivity only, whereas Datastar is more fine-grained and provides frontend and backend reactivity. They’ll continue to co-exist, so no need for a migration guide.
comment in response to
post
The framework has been around for a year and a half, and I’ve just spent the past two months of my life helping design the perfect API for it. It’s young and ready!!
comment in response to
post
For new projects, I’d recommend Datastar. Unless perhaps your use-case is form heavy – we're still working out how to make working with forms easier using Datastar.
comment in response to
post
I also rewrote Datastar’s Getting Started guide, which is a great way to learn about how reactivity works in Datastar, with interactive examples.
data-star.dev/guide/gettin...
comment in response to
post
How do you get front-end reactivity without Sprig? Do you use a front-end JavaScript framework like some kind of monster?!
comment in response to
post
Needed this, thanks!
comment in response to
post
👋