hey Alex, I hope you are well. Datastar has had direct support for req/rep of HTML, JS, JSON while still morphing for a quite a while. They allow you to go as coarse as you want. Give the size and ability to choose what plugins you actually need seems like Datastar is more in line with your wants at this point. Strange times.
It's a toy example, it's suppose to show that you can be doing N things and then redirect. If you have a normal redirect immediately, just do a 307 or whatever.
Yep, we are BY FAR the fastest signal approach and built in. Datastar is just a set of tools to ture data-* attributes into fine grain reactive expressions. Everything else is a plugin.
My intent wasn't to say it is a Datastar replacement. Just to say that I used their idea of deciding where to place the returned HTML is based on the back end driving the decision, rather than the front end.
Datastar's model of doing it this way really simplifies the front end even more compared to HTMX's model of having the elements on the front end decide where to put the returned HTML.
Our community is fine, all this is coming from people so far that haven't actually used Datastar on project at any kind of scale. If this is not the case please show your code and how it effected you directly. Otherwise, it's false outrage that I and the core team care zero about.
