Also worth checking out is the recent release of RedwoodSDK: https://news.ycombinator.com/item?id=43657215
Datastar: Web Framework for the Future?
11–20 of 161 posts
Re: Datastar: Web Framework for the Future?
#12Also worth checking out is the recent release of RedwoodSDK: https://news.ycombinator.com/item?id=43657215
[dead]
Re: Datastar: Web Framework for the Future?
#13> fresh perspective, embracing server-driven architecture
This is not fresh perspective. I used to be on "team everything on server" but it's a mistake on insist on that today.
Re: Datastar: Web Framework for the Future?
#14Datastar author here... AMA, but know that Datastar is pure yak shaving for me to do real work stuff so I have no golden calves, just approaches I've seen work at scale.
Re: Datastar: Web Framework for the Future?
#15If you want a solid demo of what you can do with datastar. You can checkout this naive multiplayer game of life I wrote earlier in the week. Sends down 2500 divs every 200ms to all connected cliends via compressed SSE.
Re: Datastar: Web Framework for the Future?
#16This is the second post I’ve seen praising Datastar in the last 24 hours, and once again no mention of the requirement to punch a gaping hole in one’s Content-Security-Policy. If this is the framework of the future, cyber criminals are going to have a bright future!
That's the nature of anything that does this kind of work. React, Svelte, Solid. Alpine has a CSP version but it does so little that I recommend you just accept being a Web1 MPA basic site.
I have ideas around ways around this but it's a per language template middleware.
Re: Datastar: Web Framework for the Future?
#17This is the second post I’ve seen praising Datastar in the last 24 hours, and once again no mention of the requirement to punch a gaping hole in one’s Content-Security-Policy. If this is the framework of the future, cyber criminals are going to have a bright future!
How does this compare to HTMX (security wise)?
Same, you control your signals and fragments. So you are responsible for proper escaping and thoughtful design.
Re: Datastar: Web Framework for the Future?
#18The TODOS mini application at data-star.dev is slow and doesn't work correctly for me (checking/unchecking items isn't reliable). To me, this highlights one common problem I've seen with frameworks that insist on doing everything on the server.
Link?
Re: Datastar: Web Framework for the Future?
#19> "what is a signal?" it's another word for event
Signals have dependencies and subscribers. It's a value and publisher and subscriber if you want to be more correct.
Re: Datastar: Web Framework for the Future?
#20> "what is a signal?" it's another word for event
a signal is not a single event but rather a stream of events at given timestamps (or, if you wish, a stream where you have an Option at each timestamp)
I googled this and got a few different answers, but not this one. Is there a particular implementation you’re referring to?