working with DOs is so interesting. there's so much stuff that the operating constraints rule out, that in a world of containers you'd just said "eh, O(n) works" and it'd work fine for large n's — but here your n's can only go so far before you start hitting time/space limits!
team monorepo needs today include
* copy-on-write worktrees
* full incremental graph builds/tests
* shared caches
and like most tooling was built for small repos!
so we are not there yet
hot take: unless you are willing to reimplement git / github (like anthropic), I think monorepos are an antipattern in an age of agents
the alternative is to keep things light and make a lovely cli/mcp for agents to do search over your org's code and docs without a checkout
@Shreyassanthu77 this is great! i think the best path to impact on the ecosystem would be to figure out how to integrate it in setup-dune/setup-ocaml/opam-ci — make CI faster and cross-compilation accessible to everyone
All of the people who hated on verification and type theory, and who called our research useless for years, should probably admit they were wrong now and maybe apologize for being mean while also being wrong
i’ve seen many people say “ai is bad at teaching and explaining concepts”
this is the biggest cope and skill issue ever
it literally gives you access to 99% of the world’s knowledge and you can ask it for infinite follow up questions, explanations, visuals, videos, analogies