What comes after Git

#1

Post by rckrd » Tue, Jul 05, 2022, 4:54 AM UTC

Re: What comes after Git

#2

Post by EdSchouten » Tue, Jul 05, 2022, 5:18 AM UTC

- A client side virtual file system (FUSE), so that you can work with large repos that exceed the size of your own system.

Version control systems like Piper (Google internal) and Eden (Facebook), GitVFS (Microsoft) already do this, but adoption is marginal.

Re: What comes after Git

#3

Post by leeoniya » Tue, Jul 05, 2022, 5:25 AM UTC

> Semantic diff – Can we figure out how to use version control to have more context-aware merges? Can you believe that we still rely on a text diffing algorithm from 1976 (and its shortcomings)? Git still has trouble with file renaming. GitHub Copilot, but for merge conflicts? Semantic diff has been tried before, but language-specific implementations will likely never work.

in case anyone missed it: https://github.com/Wilfred/difftastic

Re: What comes after Git

#4

Post by stellalo » Tue, Jul 05, 2022, 5:28 AM UTC

> I saw the pain points of git

What are these? Asking for real: it’s the second time I read a similar sentence on HN this week, without finding any specifics, so I’m curious

Re: What comes after Git

#5

Post by PawBer » Tue, Jul 05, 2022, 5:34 AM UTC

stellalo wrote: post #4

> I saw the pain points of git What are these? Asking for real: it’s the second time I read a similar sentence on HN this week, without finding any specifics, so I’m curious

You can treat the points in the article as those.

Re: What comes after Git

#6

Post by spencerchubb » Tue, Jul 05, 2022, 5:35 AM UTC

stellalo wrote: post #4

> I saw the pain points of git What are these? Asking for real: it’s the second time I read a similar sentence on HN this week, without finding any specifics, so I’m curious

that's what the whole rest of the article is about :)

Re: What comes after Git

#7

Post by kache_ » Tue, Jul 05, 2022, 5:36 AM UTC

Nothing. Keep it simple. There's a reason it has stuck around

>inb4 it isn't simple

it is

Re: What comes after Git

#8

Post by bergenty » Tue, Jul 05, 2022, 5:38 AM UTC

stellalo wrote: post #4

> I saw the pain points of git What are these? Asking for real: it’s the second time I read a similar sentence on HN this week, without finding any specifics, so I’m curious

I’m not qualified to go into specifics but I hate it. All version control needs to do is pull, push and branch. Version on branch is newer? You need to pull down before you can check in.

Instead what we get is over complicated nonsense with commits and stashes, rebases and heads, reparenting etc. I get it you don’t want to store your code on your local machine but that’s what backups are for, that’s not what the version control system should be doing.

Re: What comes after Git

#9

Post by oconnore » Tue, Jul 05, 2022, 5:40 AM UTC

stellalo wrote: post #4

> I saw the pain points of git What are these? Asking for real: it’s the second time I read a similar sentence on HN this week, without finding any specifics, so I’m curious

Perhaps, instead of trying to identify issues with git, think about how really deep team based collaboration works in other programs (say, online video games?) and then work backwards to see if there are opportunities in code collaboration tools.

Of course, just making an IDE multi-player would introduce chaos. What if the tool solved that chaos?

Re: What comes after Git

#10

Post by crmrc114 » Tue, Jul 05, 2022, 5:40 AM UTC

leeoniya wrote: post #3

> Semantic diff – Can we figure out how to use version control to have more context-aware merges? Can you believe that we still rely on a text diffing algorithm from 1976 (and its shortcomings)? Git still has trouble with file renaming. GitHub Copilot, but for merge conflicts? Semantic diff has been tried before, but language-specific implementations will likely never work. in case anyone missed it: https://github.co…

git mv?