17 ms·
Why SQLite does not use Git (2018)
- willtemperley 3y agohttps://git-man-page-generator.lokaltog.net https://git-man-page-generator.lokaltog.net is the funniest thing I've seen in a while
- BuckRogers 3y agoIt’s funny because it’s true.
- drgo 3y agomy favs commands are git-tease-chain git-scrub-dangling-object git-seize-mailmap git-dress-graft git-strangle-tree git-satisfy-daemon git-pat-tree-object
- jasonjayr 3y ago> git-erase-working-treeshould be used when you want to cautiously erase the current working tree of an upstream root and the config, and want to quiltimport to a active GUI. sounds useful!
- bobmaxup 3y agohttps://git.savannah.nongnu.org/cgit/quilt.git/tree/quilt https://git.savannah.nongnu.org/cgit/quilt.git/tree/quilt
- emmanueloga_ 3y agohttps://users.suse.com/~agruen/quilt.pdf https://users.suse.com/~agruen/quilt.pdf
- failuser 3y agoOmg, > git-molest-headincorrectly molests upstream heads using remote indices, while performing suitable hooks to tabulate the given heads. This is a bit too edgy.
- mike_hock 3y agoDoesn't really sound that convincing. Needs moar LLM sauce to make it bullshit better.
- bunga-bunga 3y agoIt took me too long to realize this wasn’t real. Git does have some awkward commands I’m not even surprised anymore.
- NBJack 3y ago[flagged]
- messe 3y ago> Otherwise, the fact that it didn't survive the front page of HN bodes ill for its reputation It’s working fine on my end?
- deleted 3y ago[deleted]
- georgemcbay 3y agoSite worked fine for me, but in any case, SQLite is 23 years old now and widely used all over the place and well understood by many thousands of developers... the time has long since passed when its reputation might hinge on the moment-to-moment uptime of its own home page.
- ogurechny 3y agoIt's probably not availability issues. From what I've seen in Fossil discussions, sqlite.org is just a couple of Fossil instances (code and documentation) and a pack of HTML pages behind a simple web server. They had to invent an ad-hoc scrape protection for computationally expensive requests, and probably have something like that for DoS protection. It is possible that it is not fair because of simplicity, and temporarily blocks certain amount of less lucky visitors. Intermittent inaccessibility of project websites seems regular to me.
- deleted 3y ago[deleted]
- Thaxll 3y agoI think the explanation does not make any sense in 2023, if 99.99% of dev use Git you have to use Git, using your own solution that no one else uses or know or need to know is bad. If you want to make your project more open to contribution you have to use what the rest of the industry is using. Edit: After reading some responses, I'm really surprised that sqlite does not accept contributions.
- enigmurl 3y agoSure, but with that kind of argument will we ever be able to make the switch to a better vcs if one exists? You have to start somewhere.
- casion 3y ago> If you want to make your project more open to contribution This is a key point, and assuming this in the positive is often a mistake. Not all projects want, or can handle, increased contribution.
- grayhatter 3y agosqlite is actually a perfect example of a project that specifically excludes public code contribution. https://www.sqlite.org/copyright.html https://www.sqlite.org/copyright.html
- upon_drumhead 3y ago> If you want to make your project more open to contribution you have to use what the rest of the industry is using. They don't want contributions https://www.sqlite.org/copyright.html https://www.sqlite.org/copyright.html > In order to keep SQLite completely free and unencumbered by copyright, the project does not accept patches.
- eska 3y ago> from people who have not submitted an affidavit dedicating their contribution into the public domain. Don’t spread FUD
- NBJack 3y agoI think there are some legitimate criticisms of Git here. But some of them are...odd. Despite using Git in a variety of circumstances, from a local personal repo project to very large company repos, I admit I haven't run into about half of these issues. > The closest I have found is the network, which is slow to render (unless it is already cached), does not offer nearly as much details, and scarcely works at all on mobile. I hope my team never has to consider their mobile device as a way to check the status of a branch. It hasn't even crossed my mind as a use case. Does this come up often for others?
- mintplant 3y agoAll the time. I would say at least 50% of my code browsing is done from my phone. I make heavy use of the mobile GitHub web interface for this (find-references support has been a godsend, search is still meh, I hate how they keep breaking basic find-in-page with SPA jank). Also Searchfox [0] when I need to comb through Firefox code (fast, excellent, no complaints—well, I guess blame on mobile could be better). Context: grad student, programming languages and systems research plus a bunch of IoT hacking on my own time. Either elder Gen Z or youngest possible Millennial, depending where you put the cutoff. [0] https://searchfox.org https://searchfox.org
- inferiorhuman 3y agoYeah, I can't say enough bad things about the Github refresh. The whole thing feels like it was done by people who've never used git (or any SCM) before. It's not just the find-in-page, it's the navigating branches, text selection, keyboard navigation within a page, and general rendering performance that have taken a huge hit. And, of course, all the side effects of requiring javascript to render text.
- FpUser 3y agoCan't imagine reading code on those tiny screens.
- jpc0 3y agoAnd this is why you should stick to an 80 column limit. It's only a pain when you decide your codebase is fine with 120+ columns because "everyone has a widescreen monitor" except no they don't. What if I like vertical monitors, or want 5:4 etc.
- BuckRogers 3y agoI’m sure git is less than ideal. I pretty much just know enough to do what I need to do with it. The only reason I want to use it is because it is the industry standard tool. Otherwise Hg, Perforce, have all had pretty compelling arguments put forward for their use. There’s so much technical churn in this industry, that any time I can use something that’s widely embraced I’m actually happy for that. Regardless of my personal feelings on it.
- qaq 3y agoI'd choose git over perforce any day.
- ninepoints 3y agoI use git primarily, but if you work on a project that needs to version control data (images, textures, meshes, sky boxes, terrain, etc.), git, even with LFS, is such a terrible experience compared to Perforce.
- mbfg 3y agodoesn't perforce only allow one branch per repo? Or is that something they addressed.
- ninepoints 3y agoI don't know that this was ever the case.
- CoastalCoder 3y agoSlight tangent, but the Corecursive podcast has an excellent interview [0] with Richard Hipp, creator of SQLite. [0] https://corecursive.com/066-sqlite-with-richard-hipp/ https://corecursive.com/066-sqlite-with-richard-hipp/
- ohthatsnotright 3y agoI'm glad Fossil works for them, but this line is bothered me: > In contrast, Fossil is a single standalone binary which is installed by putting it on $PATH. That one binary contains all the functionality of core Git and also GitHub and/or GitLab. It manages a community server with wiki, bug tracking, and forums, provides packaged downloads for consumers, login managements, and so forth, with no extra software required git, for all its issues, is not bundling the kitchen sink. I do prefer the "do one thing and do it well" approach.
- queuebert 3y agoFrom an ABI perspective, there's not a huge difference, mostly just where the code resides on disk, all local or scattered across multiple inodes.
- panzi 3y agoI think the point is that there is the option to have only git, which reduces the attack surface of only that tool, if you don't want/need anything else.
- Dylan16807 3y agoMy git seems to be mostly a single binary, and it's larger than fossil.
- jayski 3y agoI think SQLite is fantastic and Richard is obviously a genius. But I always found his obsession with single binary monoliths odd. As you mentioned it goes against the Unix philosophy of do one thing and do it well. To me it's obviously cleaner to divide a system into components that can later be swapped or modified independently.
- bane 3y agoI have no idea why Richard focuses on such things but: I'm old enough to remember when developers spent time making sure they could plow all of their build assets into a single binary distributable. It often had kind of a zest to it and when you dealt with software had directories full of stuff it looked both "corporate" and "sloppy". I've never quite gotten over the feeling that the piles of dynamically linked libraries hasn't helped things. I know objectively that there's a notion that you can update libraries instead of applications, but it feels like it makes updating applications fragile and you inevitably end up in some kind of dependency hell. "But breaking insecure applications is a feature!" I mean, okay, I guess. But I still need something to work and don't want to spend all day fixing broken layers of dependent stuff. If I have to do that, I may as well just update a single binary. Go seems to have come back around to this style of thinking, and in a sense container images and JAR files are often trying to replicate what it's like to just download a binary, chmod +x it, and execute it.
- AceJohnny2 3y agoPrevious discussions: - 2021, 356 comments: https://news.ycombinator.com/item?id=29125934 https://news.ycombinator.com/item?id=29125934 - 2018, 608 comments: https://news.ycombinator.com/item?id=16806114 https://news.ycombinator.com/item?id=16806114 I'm sure there are others, but the fact that the same document can be found through various paths (without www domain, without /drafts/ path, or without /matrix/ path) makes it harder to find previous postings.
- jaimex2 3y agoI know about 5 git commands and have worked with gitflow and feature branch repos for years now. I can't say I've ever had to think about anything or longed for a better system. And yeah, I've also done the xkcd hack when things refuse to smash together. Works for me. As long as the Visual Code git blame extension keeps telling me line by line what ticket/issue was put when I'm happy.
- EVa5I7bHFq9mnYK 3y agoI don't remember a single git command by heart, just there are some icons in the lower right corner of my Visual Studio window and in VSC window and it's pretty obvious what to do.
- avgjo 3y agoI've used Fossil for a private local project. It's quite a capable revision control system with a very decent web UI. Just a word of warning - make frequent backups of the backing sqlite repository database. I had upgraded fossil to make a few commits and then I inadvertently made a commit using an older version of fossil and it corrupted the fossil repo database irreparably and a few days' of work was lost. I've never had GIT corrupt a repo in ten years of daily use - regardless of version.
- SQLite 3y agoI dispute this claim. The underlying artifact format for Fossil is compatible back to the beginning. There have been enhancements, but nothing that would break. And there have been no reports of breakage among the countless users on the Fossil Forum. I suspect what the OP encountered was that he checked in some things using a newer version of Fossil that had enhanced capabilities. (For example, Fossil originally only use SHA1 hashes, but was enhanced to support both SHA1 or SHA3 after the SHAttered attack.) Then the OP tried to extract using an older Fossil that didn't understand the new feature and returned an error. I'm guessing at this, of course, but that seems like the most likely scenario. I have never once made a backup of SQLite repo or the Fossil self-hosting repo, or any of the other 100+ Fossil repositories that I have at hand. I've cloned the repos to other machines as disaster protection. In fact, I have cron jobs running on machines all over the world that "sync" critical Fossil repositories (such as SQLite) once an hour or so. But I have never even once made a pure backup. I did have the primary SQLite repo go corrupt on my once, years ago. Somehow, file descriptor 2 got closed. Then when the SQLite database that is the repository was opened, it opened on file descriptor 2. Then some bug in Fossil caused an assert() to fire which wrote on file descriptor 2, overwriting part of the database. I restored the repo from a clone, fixed the assertion fault in Fossil, and enhanced SQLite so that it refuses to use a file descriptor less than 3. See also: https://fossil-scm.org/home/doc/trunk/www/selfcheck.wiki https://fossil-scm.org/home/doc/trunk/www/selfcheck.wiki
- maxxk 3y agoIs it a known behavior? Considering SQLite developers approach to reliability, I think it would count as a critical bug worth fixing.
- blagie 3y agoMost of these arguments are nonsense. "Standing up a git server is non-trivial." It's literally just "git init" and providing ssh access to the directory. Most of the other ones seem to suggest the author never learned git. git has a beautiful data model and a horrible user-space to poke at it. Writing a new user-space makes sense. This seems to poorly re-invent the data model, by virtue of not bothering to understand git. The only argument I buy is: "2.6. Git provides a poor user experience," and the xkcd is not an exaggeration.
- cosmojg 3y ago> The only argument I buy is: "2.6. Git provides a poor user experience," and the xkcd is not an exaggeration. Oh no. I'm the guy in the alt text. Should I be concerned?
- thayne 3y agoIt is non-trivial to stand up a redundent, highly-available, and scalable git server. And if you throw in "with a good web interface", even moreso. But I doubt that is trivial to do with fossil either.
- velcrovan 3y agoWhat do you mean by redundant, highly available? Under what circumstances are those necessary? Whatever it is, seems completely orthogonal to version control software. Anyways, I can serve a fossil repo with a great web UI and a few 9s of reliability on an existing web server with literally a 2-line CGI script.
- blagie 3y agoRedundant? I think at some point, you missed the point of a DVCS. Scalable? When do you run into issues with git server scalability that an 80486 couldn't handle? Highly-available? At this point, just pay for !@#$ github. But it's a heck of a lot easier to do this in a DVCS than in fossil. Options: - Set up two servers. Add a hook to push from one to the other whenever a change happens. If the main server goes down, swap to the backup, and bring up a new one as a backup. - Store the git repo on a redundant, highly-available, scalable file system, and run a few git servers on the shared file system. Back in my day, we'd use AFS for this. The nice thing about the data model is these solutions /work/. The basic git data model* won't be corrupted if multiple systems are writing to it more-or-less simultaneously. Absolute worst case is the tree splits and you've got a detached head somewhere, but no data is lost. * I can't speak for some of the more advanced stuff (packing, compression, etc.), since I don't fully understand it; but it's possible to disable all of that.
- somenewaccount1 3y ago>Git focuses on individual branches, because that is exactly what you want for a highly-distributed bazaar-style project such as Linux. Linus Torvalds does not want to see every check-in by every contributor to Linux: such extreme visibility does not scale well. Contrast Fossil, which was written for the cathedral-style SQLite project and its handful of active committers Ugh...so after all that fanfare of how amazing fossil is, the author admits it just doesn't scale well. I was wondering how that "see it all" approach worked for a busy repo, and now I know, it just doesn't. I love SQLite, and glad the primary author is happy working on it with fossil. I think if he published it's largest downfall first, it might gain more adoption to folks that could actually use that feature.
- soerxpso 3y agoPersonally I see "doesn't scale well" as a feature, if I'm evaluating something to use on a personal or small project. Tools with clear limits on what they're not for usually have a more polished experience for what they are for.
- somenewaccount1 3y agoWhich is why I said he should be more upfront about it. I had to find that statement buried after 30 minutes of reading how amazing fossil was.
- ezekiel68 3y agoIn that case you might really love "...SCons, a popular Python-based build tool. In a nutshell, my experiments showed that SCons exhibits roughly quadratic growth in build runtimes as the number of targets increases" [0] [0] https://blog.melski.net/2013/12/11/update-scons-is-still-really-slow/ https://blog.melski.net/2013/12/11/update-scons-is-still-rea...
- oxfordmale 3y agoI have a love hate relationship with Git. It is current used for a lot of purposes it was never designed for by Torvald. It is time for something better, unfortunately Fossil isn't likely going to be a Git successor.
- blitz_skull 3y ago[flagged]
- jmull 3y agoYou think the lead developer of sqlite may not be cut out for software development? Also, what does 2023 have to do with it?
- blitz_skull 3y agogit has been around since 2005. It's ubiquitous. And yes, I think it's a short-sighted and not-great decision to build your own version control system. Whether you're the lead developer of the unix kernel or just some guy writing your own scripts, it's not a good decision. Your title doesn't have much to do with that.
- brisketbbq 3y agoWho should have written git and fossil? Both were written by people who had problems to solve. Should they have waited around for someone to solve their problems?
- yjftsjthsd-h 3y ago> It’s easy one of the most powerful, flexible, Probably, yeah. > and if you take the time to learn it, SIMPLE models for version control. ... And there it all falls apart. In practice, git requires a massive amount of learning to use competently, to the point that using something else just to avoid the learning curve is fairly reasonable.
- junon 3y agoAs someone who has learned the ins and outs of git, I struggle to think of a better model for revision control. I never have issues with it anymore, and it took maybe a day to learn how it works under the hood. There's a great article on git internals directly in the git manpages.
- 3y ago
- mbfg 3y agoi guess you use what you have, and don't use what you don't have, but i don't really know when i've ever thought let me see what happened after that branch was merged into future. I do have a simple script that will list what branches were merged into the current branch in git. That is useful, so being built in, in Fossil is useful i guess. My gripe with Fossil, is not technical, it is really just who uses it? How much support does it get. When will it wither and die? Maybe that is an invalid concern on my part. But that is way more important to me than any technical issues raised here.
- nmz 3y agoGiven that fossil is an integral part of sqlite, it will wither and die when sqlite does. It's also the perfect example and test of sqlite itself, an scm that is a one stop shop for the entirety of the project, remaining as responsive no matter the increase of the scm db itself.
- JonChesterfield 3y agoSqlite is going to outlive basically everything. That's not a serious hazard.
- zeroimpl 3y agoSeems like a textbook example of NIH to me. By the time you understand git well enough to design a good replacement, you’re bound to be an expert and ought to appreciate more the design of git. If you don’t like the lack of a good GUI or web application, you can just build one that works the way you want and still works with git.
- tootie 3y agoNot to be whiny, but we had better versions of git before git was the standard. I'm thinking specifically of Mercurial.
- zeroimpl 3y agoI thought they both started at the same time? Unless you are implying early versions of git were worse, which wouldn't surprise me. I know git has a learning curve, but the only times I really see junior people have issues is when they are trying to do things that wouldn't have been easy with earlier VCS systems either. And it seems like git isn't going away, so it's worth putting the time into learning it.
- happymellon 3y agoAs someone who used Mercurial for many years when I worked at a company that used because they used BitBucket, you are overblowing the situation. The CTO was very vocal about how Mercurial was better, but all the use cases he toted weren't really that meaningful. Eventually when BitBucket removed Mercurial support we switched to git. I'd used git previously and hadn't really understood the advantages of hg, and after we switched to git there was no difference in productivity. Mercurial wasn't better, it's just slightly different enough to have a holy war over.
- nwallin 3y agoGit came before Mercurial. Both git and Mercurial were spawned by the same event; BitKeeper revoking its free license for Linux kernel development. Git development began 2005-04-03, and was self hosting on the 7th. The next minor release of Linux used git as its SCM. Mercurial was announced on 2005-04-19, and has been self hosting since 2005-05-03. Original git commit: https://github.com/git/git/commit/e83c5163316f89bfbde7d9ab23ca2e25604af290 https://github.com/git/git/commit/e83c5163316f89bfbde7d9ab23... Original Mercurial commit: https://repo.mercurial-scm.org/hg/rev/9117c6561b0b https://repo.mercurial-scm.org/hg/rev/9117c6561b0b
- kasperset 3y agoI saw this video few days ago which describes some of the alternative to Git and of course Fossil is one of them. I have used Fossil in some projects and found to be ok. I found Pijul https://pijul.org/ https://pijul.org/ described in this talk to be very interesting. It was discussed on HN before. Source: https://www.youtube.com/watch?v=M4KktA_jbOE https://www.youtube.com/watch?v=M4KktA_jbOE
- jpeeler 3y agoI'm still trying to wrap my head around this one, but jj is interesting: https://github.com/martinvonz/jj https://github.com/martinvonz/jj
- brigandish 3y agoI’ve used jj on a couple of small personal projects and it was fine, but I needed to get my head out of “git mode”. The lead developer is very helpful.
- pkulak 3y agoPijul has always fascinated me. It’s like the holy grail of version control. But for my personal projects, I develop in a straight line anyway, and I’m not in control of what’s used at work, so I’ve never really used it.
- xelxebar 3y agoCheck out https://github.com/martinvonz/jj/ https://github.com/martinvonz/jj/. It's highly inspired by Pijul, among VCSes, and uses a git backing store, so you can use it personally and (mostly) seamlessly interact with any git-only team.
- toastal 3y agoPijul will be ready when it support the ability to email patches as a universal fallback method of submitting patches upstream for those that do not wish to create an account with a given service.
- thunderbong 3y agoIMHO, for software developers, a version management system is a tool, just like an IDE, or the underlying OS. The less they need to fiddle with these tools, the more productive they are. Having worked with multiple version management systems, for me, Fossil hits the perfect sweet spot. You literally just set it up and forget about it.
- friend_and_foe 3y agoI read this years ago, and it really showed me the light. I've used fossil and run it on my own server and it is a dream to work with. I hate working with git, but I do it reluctantly. I'd rather use fossil any day.
- nmz 3y agoI as well, my only gripes with it is there is no firefox persona or some sort of oauth, one of which anybody could contribute to the project without having to sign up. That way everything would be distributed and also easy to contribute and use.
- sixthDot 3y ago> The closest I have found is the network, which is slow to render (unless it is already cached), does not offer nearly as much details $ gitk --all not mobile however
- JaDogg 3y agoWoah, this sent me down a rabbit whole. Probably the best thing I saw for a long time. Seems like you can use this and mirror in Git/GitHub as well. https://fossil-scm.org/home/doc/trunk/www/inout.wiki https://fossil-scm.org/home/doc/trunk/www/inout.wiki. Builtin UI looks OK. (Usable and easy to navigate actually). But I was hoping the UI support commit as well. (I could not figure this out in UI). (so you don't have to mix command line and web interface to get things done) I think if we can build a wrapper UI around fossil (which allows open, init, commit, sync?, sync-with-git, start-web-interface) (or even better add it to fossil itself). Then, this would be highly helpful to less-techy or non-devs that code (bio, math, data-science, etc) to maintain Jupyter notebooks,etc. Hmm, but perhaps a simple git-ui client can be used for that as well. (but you will loose the builtin wiki/tickets). And ability to work locally is useful as well (but then git can do that too). In any case I have seen less-techy people shy away from git (or version control in general). I can see the potential in builtin wiki and tickets in same repo. One file to backup is also interesting.
- ThinkBeat 3y agoI am not a Git fan. The most perplexing to me is how huge companies spend 100.000s (1.000.000s??) of $$ to hack Git so that it will git with their needs. Like Google. One of the biggest issues seem to be the size of the repo, which takes days (?) to download and get started. Does Google contribute all their extra services / tools to make Git for work for then?
- mindsuck 3y agoGoogle uses piper, not git
- wodenokoto 3y agoIsn't Android on git?
- SubjectToChange 3y agoAOSP is a distributed as a bunch of git repos, but Google uses an in-house VCS called piper.
- SubjectToChange 3y agoMicrosoft is a better example with git vfs and now Scalar.
- junon 3y agoUnless you're checking out old commits, `git clone --depth=1`. Then you get close to the ideal download size for any given repo.
- gardenhedge 3y agoIf that is ideal why is it not the default?
- junon 3y agoBecause it's unexpected behavior and not what you want most of the time. It's ideal in the sense of bytes on the wire.
- Guvante 3y agoI think git gets a bad rep because no one can agree how to use it. GitHub PRs vs pushing a branch, rebase vs merge are just two examples of tools that do identical things in fundamentally different ways. And the problem is none of them are wrong. Rebasing minor commits simplifies unnecessary complexity in your history. Merging preserves what actually happened which can provide insight into why changes occurred. Of course reverse merges are the worst but that is a can of worms... When pushing to a branch you can never force push but you always force push a PR branch... Hell sometimes the easiest things create unsolvable rifts. I know of the main repo as origin and fork for my fork. Some have learned that the main repo is upstream and origin is your fork. Neither is necessarily wrong but good luck being clear when origin can refer to two locations with such extreme use cases.
- ozim 3y agoTo paraphrase Bjarne Stroustrup, there are only two kinds of version control systems: the ones people complain about and the ones nobody uses.
- jorvi 3y agoReminds me of what Bungie said in one of their GDCs. They don’t mind it (too much) if people get heated on their forum or subreddit, because people who care about Destiny are the ones that get worked up. It’s when most stop complaining or praising that they get worried, because it means apathy has set in.
- samtho 3y agoThis is a bit of wisdom that is easy to miss when you are developing a product. When people are getting worked about something and are very vocal, positive or negative, it means they care in some way. Instead of going into the doom spiral of “nobody likes what I’m building,” you can reframe it to be, “people are very passionate about what I’m building,” which is a better way to start the discussion of how to make what you have better. The opposite of love is not hate, it’s apathy.
- 3y ago
- lifeisstillgood 3y agoI tried fossil a while back mostly because of the idea of tracking tickets in the SCM. I have come to understand tickets are almost a means of communicating outside of the SCM and with software illiterates it's hard to get them to use any SCM. The thing I want most to replicate in git is "technotes" - I can get partway there with tagging and a "notes" directory but there is a lot more road to go down
- anon35 3y agoMade a list of all the revision control tools I've used over the decades, the year they were created, and the year I last used them: sccs 1973 2000 rcs 1982 2000 cvs 1990 2004 clearcase 1992 2004 perforce 1995 2011 subversion 2000 2015 mercurial 2005 2015 git 2005 present So, at least for me, they last around 15 years or so. But often time when I tell juinors that when they're my age, git will be distant a strange memory to them, they look at me funny. It's a wonderful tool and earned its success, but I'll be sad if it's our final take on the problem.
- deleted 3y ago[deleted]
- test1235 3y agoSo it looks like you're ready for a change ... What's next on the horizon?
- Zacharias030 3y agoGenerally git‘s support for a stacked PR workflow is poor [0], but imho that is the future of team collab (git is great for very asynchronously built projects, like the linux kernel). I also wonder, how much better git could be if it was based on DAGs not trees (I may want to use a changeset that is still developing in more than one branch without maintaining copies of it) and corollarily I‘d like to rebase subtrees (sub-DAGs) instead of single branches. I have introduced a stacked PR workflow to our team a while ago and a few months later half of the team had migrated to some kind of stacked PR workflow tool (on top of github and git, even though support is sub-optimal). It seems like this is an idea that is really sticky. [0] https://github.com/ezyang/ghstack https://github.com/ezyang/ghstack
- eru 3y ago> I also wonder, how much better git could be if it was based on DAGs not trees [...] Git generally supports DAGs. > [...] corollarily I‘d like to rebase subtrees (sub-DAGs) instead of single branches. Rebasing is something you do to the commit graph, which is a DAG. Branches only come in incidentally. Branches in git are really just mutable pointer to immutable commits. What you are describing is probably some useful workflow, I guess?
- toastal 3y agoI've been getting the hang of darcs recently. There's been your typical hiccups of learning something new, but it’s been an interesting process. I wouldn’t be surprised to see a Patch Theory-based DVCS be the Git successor, & if true, darcs will be the early inspiration and the terminology would likely be copied from darcs when in doubt so it doesn’t feel like a waste to learn. It’s definitely not a beta software supporting all the necessary basics for DVCS. Considering my biggest gripe is reliance on a Haskell module for SSH that doesn’t support ed25519 keys, there aren’t many issues.
- asnyder 3y agoSorry to tell you but git won out over darcs back in the very beginning. I loved darcs, unfortunately everyone else got on the git bandwagon. Fortunately darcs has built in conversion to git so all is not lost! Unfortunately though you do lose some of the pleasantry of darcs but such is life...
- _a_a_a_ 3y ago> In contrast, Fossil is a single standalone binary which is installed by putting it on $PATH. ... It manages a community server with wiki, bug tracking, and forums, provides packaged ... Standing up a community server for Fossil takes minutes. Let's see... About a year ago I try to set up fossil because I wanted the issue tracking it supposedly provides. I'm already using git for VC and will stick with it. Spend several hours and got nowhere. It's a local web-based thing and all I kept getting back was 404 Not Found. Did some reading around, found somebody had solved the problem by using --force option (IIRC, to force creation of a repo) but that didn't get me to anything actually working. The docs were unhelpful, as in wrong. Gave up. If you can't document your software then don't release it. Certainly don't make claims for its greatness and ease if you ignore what your users are saying on your message boards.
- JonChesterfield 3y agoMake a repo. That's a file that lives wherever. Go to some directory, fossil open filename. Now you have a working directory. Type fossil ui, now you're looking at it in a browser. It sounds like you want a version running on a machine that multiple people log into to access the UI. That I don't know how to set up. Spinning up the UI locally makes a lot more sense to me that sharing a single instance with the world.
- _a_a_a_ 3y ago> Make a repo. That's a file that lives wherever. Go to some directory, fossil open filename. Now you have a working directory. Type fossil ui, now you're looking at it in a browser. Don't remember where I got to, I think --force got me a repo finally but the browser, well, I just got 404 then gave up. > It sounds like you want a version running on a machine that multiple people log into to access the UI Nope, mine is a one-man project, simple as you like.
- gardenhedge 3y agoI've used SVN and GIT and I agree that Git is needlessly complex. The tooling around it (that I have used) is better though.
- eru 3y agoI don't necessarily agree with the author, but it's still an interesting and thought-provoking write-up. I'm also happy someone is willing to put time and effort into keeping alternatives alive: I like git, but monocultures are seldom good.
- Mizoguchi 3y agoSpent many years on Subversion and Mercurial before moving to Git. I agree that it may be complex if you don't take the time to understand the fundamentals. I made the mistake to jump right at it on a very large project thinking my experience with other non distributed systems would be enough. So I had to take a step back and dedicate some time to read documentation including visual examples of the most common situations I encounter. Merging and resolving conflicts are those of two situations where I struggled the most particularly when working with sub branches in large projects (5+ developers) with a very fast pace of development. Once you understand the fundamentals (you can confidently draw on paper the current and future state of the tree after your changes) Git is not difficult IMO and 99% of the time you can work with a dozen of commands if you have discipline to use standards and do frequent housekeeping. If you let changes and branches go for two long without committing, merging and deleting them, never tag and release, write poor commit messages and don't reference issue numbers, lack naming conventions, submit dirty PRs and let PRs sit for days and weeks before approval, etc, then the problem isn't Git.
- SQLite 3y agoThe link is to a debugging and testing version of the document. Notice the "debug" in the URL: "https://sqlite.org/debug/matrix/whynotgit.html https://sqlite.org/debug/matrix/whynotgit.html" The correct link is https://sqlite.org/whynotgit.html https://sqlite.org/whynotgit.html