3 ms·
>I didn't use Git when it first came out. This really hinges on what you mean by "didn't use git". If you were using bzr or svn, that's one thing. If you wer
by linsomniac 7mo ago
>I didn't use Git when it first came out.
This really hinges on what you mean by "didn't use git".
If you were using bzr or svn, that's one thing.
If you were saving multiple copies of files ("foo.old.didntwork" and the like), then I'd submit that you're making the point for the AI supporters. I consulted with a couple developers at the local university as recently as a couple years ago who were still doing the copy files method and were struggling, when git was right there ready to help.
- intrasight 7mo agoPretty sure he meant he didn't use Git. I'm still stuck with TFS and SVN in my day jobs but use Git on and off on side projects. I really wish all my clients would just switch to Git.
- ambicapter 7mo agoGit is old and busted, jj is the new hotness.
- jmye 7mo agoWas "when it first came out" a confusing limiter, there? I guess it seems like the article was making the point that jumping on git the day it came out could've just meant learning the betamax of repos, and that it was better to wait a bit to see what mature tech looked like, rather than waiting until 202X to realize that saving multiple file versions was suboptimal. I don't understand how this, at all, makes "the point" for anyone.
- LeonidasXIV 7mo agoUsing Git when it came out would have probably meant to use Cogito, which has been dead for such a long time by now. Or have bet on Mercurial. Which is also close to dead. Or darcs, which has been big in certain environments and now practically extinct.
- xigoi 7mo agoGit may have an arcane interface, but if you learn it, you can be sure what exactly will happen when you run a Git command. Unlike with LLMs.