4 ms·
There are a couple nodejs implementations as well. I would know - I wrote one of them.
by josephg 2y ago
There are a couple nodejs implementations as well. I would know - I wrote one of them.
- junto 2y agoThis looks somewhat similar to websockets and SignalR. What am I missing here? Is it like GRPC as a protocol, built on top of HTTP/2? I’d be interested in working on a port for .NET.
- josephg 2y agoIt’s like how http and tcp are different. Http adds a semantic layer on top of tcp which describes fetching documents and updating them. Of course you could make your own nonstandard http on top of tcp, but having a consistent protocol that everyone uses means we can have content-agnostic tooling and middleware for caching and fan out. When you use http, there’s a lot of existing tools that will just work and be compatible with your software. That’s what we want for braid. Braid is an extension of http which adds semantics for documents and data that change over time. (I’m no longer directly involved, but I really hope the project succeeds!)
- dotancohen 2y agoThat's great to know. The fine article mentions only Haskell and Lua unfortunately - I wonder if it is out of date.