I literally wrote Datastar because this kind of option is only available in data-* attributes if you want a spec compliant way to do this. Look at what we've been able to do given the limitations of that spec. Please reach out if you want a whole lot of old man ranting at clouds www.data-star.dev

y'all might be interested in our approach. data-star.dev
Life get a lot easier when you put state in the right place and keep things declarative.

Hypermedia is production of state. If you think that's trolling this is the wrong career for you

You must be pretty new to what the concept of hypermedia is. Welcome! Lots to learn!

You can do it, but man is it a bad idea

To be clear, Datastar doesn't use crdts as a recommended approach because local first for a hypermedia engine (the browser) is the mother of bad ideas for the web

Via your server, ironically the exact same way are your "local" which still gets all it's state from the backend. Seriously why not just make a real native app? It'll be smaller faster and less battery drain on your users?

I didn't tell you shit. I mentioned that being excited to hit use standards in the browser is weird. Yes, but crdts are always a massive tradeoff. I think most apps in real world are closer to bank apps where local first makes zero sense

We have approaches that save orders of magnitude less data (up to 6000x in prod) and work great in 3g on embedded devices. Try that with your svelte app

Show me where Datastar doesn't work offline? Show me where it doesn't have the fastest signal approach? data-on-offline? Must be easy to right things of when you have no idea what something is.

If you think it's like live view you have no idea what you are talking about. I'm not selling you on anything. Please tell me what is lacking since you are clearly in the know

Carson can't more about vibes than performance or actual complexity. You are right, I'm an asshole. You 💯 should keep focusing on what you are doing!