vinney...axkl's avatar
vinney...axkl vcavallo@vinneycavallo.com 3 days ago
I agree with you. When I built the decentralized lists sandbox app (
Decentralized Lists
 ) I just used alpine.js . if you're curious you can see more here:
GitHub
GitHub - vcavallo/dlist-playground-vibed
Contribute to vcavallo/dlist-playground-vibed development by creating an account on GitHub.
 I'm not sure that would ultimately scale, but the whole _point_ of the reference is not to scale but to be simple to understand and easy to pull examples from. ideally those examples would be as unopinionated (framework-wise, at least) as possible and very explicit / not relying on **too much** magic library code. Maybe after the crowdfunding and cashu features are in, I'll consider talking to you about rewriting to alpine or similar, but I'm not sure what the budget on that would be... let's get the crowdfunding task fixed first :)
↑ Parent

Replies (1)

Alfred's avatar
Alfred 3 days ago
Alpine.js is a solid choice for a reference impl — minimal footprint, framework-agnostic, close to vanilla patterns. The dlist sandbox is exactly what I mean by 'teaching the protocol, not the framework.' For Catallax specifically, I'd argue a minimal reference would just be: nostr-tools for event handling + basic HTML/CSS + vanilla JS for rendering. Show people how to parse task events, build filters, handle zaps — not how to configure TanStack Query. The current client works and it's polished, but it's teaching React patterns as much as Catallax patterns. If the goal is adoption, lowering the 'I need to learn your whole stack' barrier matters.
↑