One idea i found interesting on top: why not use a service-worker to mock the backend completely (https://mswjs.io/) and mock the server answers with the service-worker.
Then you still have a local-only PWA-style frontend and can choose yourself, how to sync it back to a server if you really like or need to.
What datastar is great for is: throw all that overcomplicated frontend-junk away and concentrate on the real innovation or simply get things done. Not to forget: ignore the dependecy-hell of every nodejs-based project you can encounter. After the lowcode-initiative, now it's time for the "nodeps"-initiative. Deprecate npmjs.com.
"With a focus on security" was the punchline and i had to smile.
While i encourage the great intention and the work that has been done, it seems an oxymoron to create a secure client to connect to unsecure clients.
I will never forget that blazing speed of the BlazeRDP-implemetation that i used in the past that is now long forgotten. I never saw such an speed-optimized RDPish implementation. I knew i was connecting to unsecure clients and used a propietary fix to a MS-based protocol, but it was insanely fast. I never had such a fast remotedesktop since then regardless of the OS. This is not an ad, i'm not affiliated, it's simply a fact in my life, that i recall.
And i forgot to mention something: the mobile client was also the best that i ever used, too. Absolutely intuitive back in the days - but i don't know how it is today. But i expect it to be even better, not degraded.
Wow, what good news! I totally love Hasura but totally missed a lot of things since graphql. My stand was, that i don't want to use a second product for vectors and i'm totally into postgres and hasura.
My question: do the newly added hasura features make it completely obsolete to add pgai as extension to postgres or can they play along nicely.
My first guess is i'll simply combine both. I want to have a stack i can work and get deeply fimilar with and not change it all 3 month, when a new funky vectordb is announced.
What datastar is great for is: throw all that overcomplicated frontend-junk away and concentrate on the real innovation or simply get things done. Not to forget: ignore the dependecy-hell of every nodejs-based project you can encounter. After the lowcode-initiative, now it's time for the "nodeps"-initiative. Deprecate npmjs.com.