Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- Right, because I want a stupid Cloudflare captcha before every git operation.by zorked
- Author of GitSocial here. It is now possible to break most hosting dependencies by using such tools as Walgit or GitSocial to store all collaboration data in git itself and pushing it all to an S3-compatible bucket. https://gitsocial.org/ is hosted on an R2 bucket. Cross-forge, cross-bucket collaboration is built in to it, further decentralizing hosting. Happy to answer any questions!by delf
- If it’s for agents why don’t you make this a challenge towards them? What sort of human element is desired here?by hmokiguess
- $25k to build the next GitHub for $125B company? How generous.by camcil
- I build things.
I build them on machines I own placed in racks I have they key to.
There aren't any resource limits to hit and legal service is brought directly to me - not to a provider nor middleman.
There also isn't a global MITM inserting itself between me and my users.
I can't imagine doing it any other way and I implore you not to build things on complex, fragile, highly abstracted foundations.
by rsync - So, one of the leader companies wants to replace the major tool used by developers all around the world, but doesn't want to pay developers to do so.
They want us, external developers, to build it for $25k... But not cash. $25k of cloudflare hosting.
Why do I feel like it's the most insulting offer I have seen in a while?
by Einenlum - We want to have less, not more, dependence on Cloudflare.
Single point of failure, for both technical and political failures.
by Animats - 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.
by btown