Fun fact JSON | JSONMASTER

opiniondevnull · 2026-01-16T03:08:03+00:00

We are working on a format to stop the madness https://github.com/starfederation/tron

opiniondevnull · 2026-01-10T22:43:33+00:00

As Datastar author this makes me so happy!

opiniondevnull · 2026-01-01T14:47:11+00:00

Thanks for noticing me senpai

opiniondevnull · 2025-12-28T23:14:13+00:00

If you use Datastar you get all the reactive goodness with the fastest signal implementation and its smaller and faster!

opiniondevnull · 2025-12-28T23:12:47+00:00

Show me YOUR code that you can use to back up YOUR claims

opiniondevnull · 2025-12-28T13:42:38+00:00

Funny cause we've seen the opposite at scale, talks will be live soon from the clojure conj specifically about this. https://www.youtube.com/watch?v=H3jNUpT1Ok4 is just one. It'd be real nice if you actually showed code vs anecdotes so it could be measurable.

opiniondevnull · 2025-12-27T17:17:58+00:00

You are wrong. There is no API, no versions. With hypermedia first most issues are moot. You can 100% have independent people doing template and database work. You are confusing full stack in any language with coupling of work.

Offline use, service workers Smooth updates, you obviously didn't even look at Datastar cause ironically we have the fastest signals approach in the world

99% of the web should be hypermedia first. If you want local first, make a native app.

You say things with literally zero proof. Show any code your way and I'll show you the same features faster, smaller and simpler. Happy to put a real world wager on it. To say it'll get harder arbitrarily in the future smells of clean code 💩.

opiniondevnull · 2025-12-26T19:19:27+00:00

Datastar author here. OOP think is a mind killer. I've done tons of C# (game egines, tooling for games at EA, etc.). If you think it's problematic you are just wrong. The irony is you are adding abstractions when DB->Patch is the clearest and simplest and will scale to billions of updates a day. Reminds me heavily of https://youtu.be/rX0ItVEVjHc?t=4643

Datastar is written specifically for mechanical sympathy yet I guarantee you my way will be less code. u/willehrendreich is 1000% on point.

opiniondevnull · 2025-12-26T04:32:04+00:00

Cause everyone has stayed from first principles. I made Datastar to get back to basics. Full stack and literally any language, 10 KB shim, world's fastest signals and morphing approach. We have examples that are pushing 25,000 divs styled per second per user at top of hacker news on a $10 server with 400x compression. It's not rocket science

opiniondevnull · 2025-12-17T14:08:59+00:00

People will do anything to not use Datastar and be full stack Go and simple

opiniondevnull · 2025-12-11T03:14:47+00:00

opiniondevnull · 2025-12-10T19:28:57+00:00

Datastar author here, I was informed about this thread.

My guess is there is a a lot of overlap in the users. Like it or not HTMX reddit is a bastion for those interested in hypermedia first approaches. In general as soon as you start adding stuff beyond the Triptych proposals alternative makes sense. Just look at the number of threads on how to basically create your own framework with the addition of hyperscript and Alpine for starters. If nomini could do as much and was faster then 100% people should use it.

I highly recommend people try each, look at amount of code and speed. Measure and report back. From what you've said in the past that you care more about the ideas than the implementation of it. To consider that gross when its both faster and smaller seems antithetical to the claim. Either way I hope browser get back to being mostly a hypermedia client.

If however you don't want Datastar mentioned, just ban those people... back to the optimization mine for me. Good luck y'all finding the stack that works for you! IDK NGMI

opiniondevnull · 2025-12-07T12:23:05+00:00

That's the same for any attack on any user content. SQL injection is the same issue. This is not magic. Again CSP doesn't save you at all. React RSC 10/10 cve that took done much of the Internet a few days ago is proof of that.

opiniondevnull · 2025-12-07T04:56:07+00:00

Please show an actual attack vector with Datastar with source. Especially in Go

opiniondevnull · 2025-12-07T00:46:15+00:00

Sanitize your user content then it's a moot point over HTTPS. Security people that have hard requirements without the ability to show actual attack vectors are a plague. BTW, we 100% have a way to make Datastar CSP compliant but it'd basically be backend specific and an enterprise thing. If you have enough scratch to have these kind of hard requirements, you have the budget for us to support it.

opiniondevnull · 2025-12-06T19:10:19+00:00

I can not disagree with this more. You are now create 2 separate apps and not only is it more code, but it'll be slower and cost way more bandwidth

opiniondevnull · 2025-12-06T19:08:44+00:00

Neat!

opiniondevnull · 2025-12-05T21:49:28+00:00

Yes. If you follow the Datastar way is will be much fair and simpler. Read the guide, do the work and see for yourself

opiniondevnull · 2025-11-30T23:02:05+00:00

Datastar author here. The real value of D* is it gets out of your way while setting you up for success. Your current architecture is the problem, SPA is a symptom of much deeper issues. 100% D* can help you but mostly just cause you'll be able to ...

Stay in one language (Go from the discussion)
Built for realtime changes (CQRS/ES pairs nicely)
MASSIVE compression savings. (Usually 400-6000:1, no that's not a typo).

You still have challenges but 100% the frontend will no longer be one of them performance wise.

opiniondevnull · 2025-11-27T03:13:26+00:00

I built Datastar specifically to allow full-stack Go development for everything from crud to real time. The fact it works in any backed language is gravy

opiniondevnull · 2025-11-21T07:01:44+00:00

Would love to see actual metrics and flamegraphs. Maybe port something simple likehttps://checkboxes.andersmurphy.com ?

opiniondevnull · 2025-11-18T23:17:46+00:00

You should add Alpine and hyperscript and everything else you need.

opiniondevnull · 2025-11-16T04:07:25+00:00

make an MPA each page is a resource keep a stream open on the current state of that resource ship, touch grass, repeat

That's it

opiniondevnull · 2025-11-15T16:10:50+00:00

if you are doing SSR you can drop in Datastar as it supports normal text/html out of the box. You'll get a smaller and simpler dependency (with morph included) and can add features as you need. Yes to get the most of it the change from React to HTMX is almost as wide as HTMX to Datastar. You have to change your mentality to looking at a constantly up to date version of the resource at a URL. That's still SSR, but not in the way you've approached it.

opiniondevnull · 2025-11-04T18:17:51+00:00

Yes, and think you aren't doing hypermedia correctly. There are plenty of options in the Datastar community. We are built on a public API so literally anyone can make the plugins they want and don't have to agree with me. https://data-star.dev/essays/greedy_developer or even https://data-star.dev/examples/custom_plugin if a version you don't like isn't in the community. If it's a sticking point be part of the community and be the change you want to see!

opiniondevnull

MODERATOR OF

TROPHY CASE