The core idea: streams get their own URL and use opaque, monotonic offsets. Clients persist the last offset they processed and resume with "give me everything after X." No server-side session state, CDN-cacheable, plain HTTP.

We kept seeing teams reinvent this for AI token streaming and real-time apps, so we're standardizing it as a standalone protocol.

The repo has a reference Node.js server and TypeScript client. Would love to see implementations in other languages—there's a conformance test suite to validate compatibility.

Happy to dig into the design tradeoffs—why plain HTTP over WebSockets, etc.

Comments URL: https://news.ycombinator.com/item?id=46209189

Points: 10

# Comments: 3

Also the team is top-notch — Sam was my co-founder at Gatsby and I worked closely with Shane and Abhi and I have a ton of confidence in their product & engineering abilities.

There's a variety of valid patterns for writes & we don't want to be prescriptive about how you do them. We aim instead to help you easily use Electric with your preferred/required write pattern.

It's possible we'll write our own write library but it's equally likely we'll continue to find it better to partner with other projects building excellent libraries (like we are with https://livestore.dev/).

Electric itself is quite scalable at reads too so for a SaaS use-case, you might not need any http proxy help.

It's dramatically faster to read from a local copy of data vs. sending the query to Postgres and can eliminate a lot of network and db load as well.

Comments URL: https://news.ycombinator.com/item?id=35186174

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=32443845

Points: 4

# Comments: 0

* like Gatsby Cloud https://www.gatsbyjs.com/products/cloud/

To reliably provide near real-time deployments, we need tight integration with the CI/CD environment to optimize and parallelize the work; that's why you’ll see the fastest builds and deploys through Gatsby Cloud — the platform is purpose built for Gatsby!

Really appreciate the feedback and support for our launch today! The team worked super hard to get Incremental Builds live in public beta but are taking all the feedback (here and all over the web) as we go into full launch. Let us know what you think. Thanks!

Typescript is rebuilding their docs on Gatsby right now and wrote up their reasoning behind the choice here: https://www.gatsbyjs.org/blog/2020-01-23-why-typescript-chos...

If you can articulate what makes Gatsby seem odd to you — I'd love to hear it!

FWIW, lots of people do love Gatsby so perhaps there was a misfit with what you were looking for

https://twitter.com/i/moments/1194814354690125825

Gatsby tries to balance making your site work at some level offline w/ not precaching too much.

By default we cache the front page & then do "run-time" caching as the user visits different pages so ensuring they can at least return to the pages they've visited when offline.

We launched our product, Gatsby Preview, into alpha in July https://www.gatsbyjs.org/blog/2018-07-17-announcing-gatsby-p...

A lot of people really love building sites with headless CMSs and Gatsby. Gatsby Preview gives content editors live preview of changes they're making in the CMS on a real version of the site.

We launched with support for Contentful and are adding support for other headless CMSs along with traditional CMSs running in headless mode like Drupal and WordPress.

Also check out our launch blog post https://www.gatsbyjs.org/blog/2018-05-24-launching-new-gatsb...