|
| taklusultan wrote:
| This could be the History of Version Control itself.
| ainar-g wrote:
| Only if it also mentioned SCCS, heh.
|
| https://pubs.opengroup.org/onlinepubs/9699919799/utilities/s...
| p_l wrote:
| With Go, you'd probably also need to mention versioned
| filesystems of Plan9 :)
| dang wrote:
| Recent and related:
|
| _The Go language 's first commit (1972)_ -
| https://news.ycombinator.com/item?id=30329279 - Feb 2022 (45
| comments)
| rossmohax wrote:
| TIL it is possible to add arbitrary "headers" , like 'golang-hg'
| to commit objects in git.
| DaiPlusPlus wrote:
| Don't think of git as a version-control system. Think of it
| more as a distributed content-addressable object store database
| representing an acyclic directed graph[1].
|
| ...with real-world applications!
| https://stackoverflow.com/questions/20151158/using-git-repos...
|
| [1] That's a lot of post-2010s buzzwords for a system written
| in 2005.
| rfoo wrote:
| You forgot to replace database with blockchain.
| bch wrote:
| > And that's the end of the story, until we move to a fifth
| version control system at some point in the future.
|
| Is this a hint, or just leaving the door open?
| ainar-g wrote:
| Probably a joke. Unlike most other mentioned version control
| systems, Git doesn't seem like it's going anywhere any time
| soon. But neither is Git eternal, heh.
| rsc wrote:
| What a sad world it would be if Git were the end of the
| story, if no one ever built a more compelling version control
| system. :-)
| zemo wrote:
| I've been using git for twelve or so years. In the last few
| years I've been working on more projects with non-programmers
| and more projects involving media and it has made me dislike
| git more and more with every passing day. I really hope git
| is not where version control stops seeing innovation; there
| are a lot of projects for which it is ill-suited.
| [deleted]
| tomphoolery wrote:
| That Brian Kernighan guy is really ahead of his time. He invented
| Go before writing the book on C!
| btreecat wrote:
| While I have learned to be mostly competent when it comes to git
| day-to-day tasks, I still miss hg for it's clean interface design
| and simplified workflow.
| yjftsjthsd-h wrote:
| Oh yeah, hg was way easier to learn, and IMO to understand. I'm
| very happy that I learned hg first and _then_ picked up git; I
| think learning hg first was "easy mode" and then extending to
| git was easier to learn in turn.
| throwaway894345 wrote:
| Agreed. It was a version control system for humans.
| Unfortunately the Hg people decided that the only stable
| interface would be the CLI, which made it infeasible to build
| the likes of GitHub around Hg, and GitHub (not Git itself) is
| what drove Git's success.
| theamk wrote:
| Can we stop with "github" narrative? I remember choosing git
| vs hg back when github wasn't a thing yet. We chose git on
| its own merits - it was much faster and had much better
| support for editing commits (it mattered for our code review
| processs). I am sure our org was not the only one.
|
| (FWIW, I think hg may have caught up in those areas.. But
| this is too late now.)
| muxator wrote:
| Hg in itself is alive and well. Interacting with git
| repositories works well with hg-git.
|
| But it is true that, for the mindset of the general public (or
| younger developers), it might well be nonexistent.
|
| It is a shame, since life with mercurial is still so easier.
| taeric wrote:
| I'm curious what makes you consider it clean? I'm specifically
| not claiming otherwise; I just don't know what that claim
| means.
___________________________________________________________________
(page generated 2022-02-14 23:00 UTC) |