Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Centralization is antithetical to the whole idea of the internet
  • Right, because I want a stupid Cloudflare captcha before every git operation.
  • The next platform for Agentic SCM is just… Fossil. Fossil is an SQLite database that can store anything an agent would ever need.
  • Cloudflare gets so much action on here, and the product they've put out the last 6-12 months has been pretty underwhelming in my opinion. Sometimes, as in this case, obnoxious even. A lot of it (most of it?) feels vibe-coded and derivative, just take whatever is big now or last month and throw "edge" on top. Anyone care for a moltworker?
  • If it’s for agents why don’t you make this a challenge towards them? What sort of human element is desired here?
  • $25k to build the next GitHub for $125B company? How generous.
  • We want to have less, not more, dependence on Cloudflare.

    Single point of failure, for both technical and political failures.

  • Sometimes I think back to Google Wave, that beautiful glimmer of real-time collaborative canvases, announced in 2009 when Angular and Backbone hadn't even been invented, and think it launched almost two decades too early.

    https://en.wikipedia.org/wiki/Google_Wave

    https://youtu.be/v_UyVmITiYQ?t=3850

    https://www.usenix.org/legacy/event/lisa09/tech/slides/berli...

    We're now in a world where we expect real-time interfaces to be developed and immediately deployed for our feedback by agents, in business-critical settings where classic SDLC timelines are far too slow, but code quality is becoming more difficult to manage at scale.

    Git, at its core, is a fundamental notion that behavior is an auditable tree of immutable changes, where any participant can rearrange or rewind or remix this sequence on a local machine to show, and interact with, a provisional combination of those changes.

    Google Wave, with its operational transformation (OT) and federation systems, was similar in many regards. We have CRDTs now, and far better techniques for auto-merging workstreams - including agentic systems that can resolve conflicts intelligently!

    Wave fundamentally had a concept that people would come together and evolve a simple chat interface, into a customized real-time application for their use cases, and that that iteration could happen in real-time, with data and behavior both evolving in collaboration with bots. Wherever Git and the broader notion of SDLC goes, I hope it brings the best of this thinking.

Explore Birbla archives