Definitely agree that Git is mediocre-at-best VCS tool. This has always been the case. But LLMs are finally forcing the issue. It’s a shame a whole generation programmers has only used Git/GitHub and think it’s good.
Monorepo and large binary file support is TheWay. A good cross-platform virtual file system (VFS) is necessary; a good open source one doesn’t exist today.
Ideally it comes with a copy-on-write system for cross-repo blob caching. But I suppose that’s optional. It lets you commit toolchains for open source projects which is a dream of mine.
Not sure I agree that LSP like features need to be built in. That feels wrong. That’s just a layer on top.
Do think that agent prompts/plans/summaries need to be a first class part of commits/merges. Not sure the full set of features required here.
> It’s a shame a whole generation programmers has only used Git/GitHub and think it’s good.
Well... I used SVN before that and it was way worse.
Clearly the poster has never encountered cvs or cvs-next.
And clear OP hasn't heard of vss..
Where I worked, before SVN we didn't even used any VCS system. Most of us were not even familiar with the concept.
I have worked with all those and more.
RCS, anyone?
Continuing the theme, a new starter at my place (with about a decade of various experience, including an international financial services information player whose name is well known) had never used git or indeed any distributed, modern source control system.
HN is a tiny bubble. The majority of the world's software engineers are barely using source control, don't do code reviews, don't have continuous build systems, don't have configuration controlled release versions, don't do almost anything that most of HN's visitors think are the basic table stakes just to conduct software engineering.
> It lets you commit toolchains
Wasn't this done by IBM in the past? Rational Rose something?
Clearcase