11 ms·
Pijul is a free and open source (GPL2) distributed version control system
- 1oooqooq 3y agoDoes it accept per-repo settings? (e.g. git config --local) Does it use proper SSH? (e.g. `git clone my_entry_on_ssh_config:/repo_path.git`)
- Aachen 3y agoThat honestly sounds like an implementation detail compared to figuring out what version control model even makes sense to begin with If you want local configs, worst case you can update $HOME inline and make it use different dotfiles. If ssh is a must, sshfs can be a way to achieve that
- 1oooqooq 3y agonot being able to set ssh parameters (and key paths, etc) via .ssh/config was a nightmare on git a long time ago. impossible to not leak identities to random servers. impossible to have curated identities for the same remote. imposible to use adhoc jump hosts. etc.
- mdaniel 3y agoI seemingly can't link to line numbers in their nest thing, but https://nest.pijul.com/pijul/pijul:main/SXEYMYF7P4RZM.ERRQA#:~:text=ssh%3A%2F%2F https://nest.pijul.com/pijul/pijul:main/SXEYMYF7P4RZM.ERRQA#... is ssh.rs in the pijul-remote directory, so presumably "yes" also, an especial :fu: to whatever the hell is going on with SXEYMYF7P4RZM.ERRQA being a permalink to a file with a specific name, forcing me to write out in english what's going on there
- 1oooqooq 3y agoyeah the web think is pretty limited. no context lines on diffs at all, and I couldn't find a link to the full-file diff from the changeset. But i wouldn't worry too much about the nest usability yet.
- baq 3y agoI'm watching Pijul from afar for years now. I'd love to see it get 1% of the investment Github gets...
- BlueTemplar 3y agoGithub also managed to succeed through being a kind of social network (think "stars"). If you care about Github's dominance being an issue, walk the walk : refuse to do bug reports through it, publicly shame people and companies that use it or advertise it.
- dash2 3y agoI use Github and I bet 99% of coders here do too. If someone tries to publicly shame me, I'll just laugh at them.
- throwaway290 3y ago> I use Github and I bet 99% of coders here do too. I know plenty of people & projects using Gitlab and Sourcehut (myself). > If someone tries to publicly shame me, I'll just laugh at them. Shaming may be wrong. You must have pretty good job security/wealth/influence to refuse Github because this can lose you many opportunities in the industry. But that doesn't make it good, only understandable & honestly sad
- patates 3y agoIf I care about one thing, I should "shame" others who do not care about it? It feels like your comment escalates things up too quickly. Could it be that you wanted to expand your thoughts in between and didn't have the time or just forgot?
- BlueTemplar 3y agoIt's a comment, not a blogpost, I am assuming some familiarity on HN with these issues, why using Github would be considered bad behavior : An actual blogpost : https://drewdevault.com/2021/12/28/Dont-use-Discord-for-FOSS.html https://drewdevault.com/2021/12/28/Dont-use-Discord-for-FOSS...
- greatNespresso 3y agopijul is a fantastic tool in the simplicity it brings compared to git + I wish it will succeed in the long run.
- ykonstant 3y agoI seem to recall very positive comments regarding pijul's underlying architecture/theory. However, as I don't have the headspace to delve into it, I would love a blurb at the beginner level that highlights the benefits of using pijul compared to other VCS, and a very brief and simple comparison between pijul and git (focusing on the differences).
- psychoslave 3y agoI think that whatever VCS come today, it will have a hard time finding a broad adoption use case that overweight the massive footprint of git ecosystem.
- bondarchuk 3y agohttps://news.ycombinator.com/item?id=39452312 https://news.ycombinator.com/item?id=39452312 This comment (that probably prompted this submission) gave me some idea at least.
- exDM69 3y agoIn day to day use, there's very little difference in the practical use of git vs. pijul. You edit files, commit then push. Of course the user interface is different and some of the terminology is different but it's still a distributed version control system. As for the differences, the advantages are listed right there on the front page: commutation, merge correctness, first-class conflicts and partial clones. Explaining these in more detail in a short example ("a blurb") is not really easy because you'd have to first set up an example three way merge (for example) and then study the behavior of git vs. pijul in detail. I recall seeing a video presentation from the Pijul authors which delved deep into this if you're interested. But I'll give it a go anyway... tl;dr: pijul can handle certain merge situations automatically where git requires you to manually resolve them
- vlowther 3y agoMore than that. If you have ever had to fix a bug in code common to multiple maintained releases of a project, being able to apply the same patch to them all as its own thing instead of having multiple cherry-picked commits with identical content would be nice.
- derbOac 3y agoI've been following this for awhile. Not my area of expertise but it seems like such a solid project. Curious to hear about any experiences using it or thoughts about how it could be improved, extended, or compares to other systems in actual use.
- jillesvangurp 3y agoAs somebody not using this, it looks like the main obstacles to this getting popular (assuming it works as advertised and it's easy to use, I wouldn't know): - Work on the pitch and clearly state the problem this is solving instead of mainly talking about the competition. What makes this unique? Why should people care? - Make it easy to start using this for teams. My guess is that this is where a lot of developers fail to convince others in their teams. Back in the day when I started using Git, interfacing with existing svn repositories was a key selling point for me. Likewise, I helped migrated a big cvs repository to subversion when that was new. Key selling point there: we don't loose our version history. This is a complex topic of course but I bet there are actually a lot of solutions here. - Show that there's an ecosystem. Who is using this? What tools are there? Are there any project hosting things that I can use? Answer these questions. This is about taking away any concerns people might have about using this that are perhaps half convinced already.
- exDM69 3y agoThis is a chicken and egg problem and I don't see a way out of it. Even if Pijul is better (not voicing an opinion here), it's not drastically better enough to replace Git in widespread use in the near term. The difference in day to day use is not huge. And it is better in handling certain merge situations that are painful in git, but most programmers don't run into these often enough to care. > What makes this unique? It's patch based rather than snapshot based. > Why should people care? It avoids certain merge scenario problems that git makes painful. > when I started using Git, interfacing with existing svn repositories was a key selling point for me Pijul can import and export to Git (and probably others) with less problems than git vs. svn (because SVN is not distributed and had a weird branching model). > Show that there's an ecosystem Here's the chicken and egg problem again. There's a "free" hosting service advertised on the front page. Or you can use it with your git hosting (but lose some of the advantages). But GitHub and GitLab have their own CI systems and other infrastructure which isn't going to be easy or cheap to replace. So yeah, I think that Pijul is a great piece of technology that solves a real problem we have with Git, but it's unlikely to overcome the inertia that Git{Lab,Hub,} have.
- cpach 3y agoAnyone using Pijul? Either in prod or for hobby projects.
- h4ch1 3y agoJust like how Sapling is compatible with GitHub, I'd love to see Pijul being compatible with GitHub wrt creating at least a read-only mirror. I've seen this exists: https://github.com/purplesyringa/PijulGit https://github.com/purplesyringa/PijulGit, but hasn't been updated in 5 years.
- gugagore 3y agoIs sapling compatible? It gets rid of your .git directory.
- charcircuit 3y agoIt's network compatible in that you can clone, pull, push, etc with a github repo.
- Murk 3y agoI have been following Pijul loosely for a while, and I would strongly agree that it could do with some information on some of the possible practical advantages of the approach. I do have some Pijul repositories around, but have not used it with the necessary further to explain any of the advantages, however, one possible advantage to note is that the equivalent of cherry-picking as used in GIT et. al, which always generates a new commit hash per cherry-pick for the same content should not happen in the Pigul world as I understand it. i.e. A specific commit when "cherry-picked" should have identical hashes, which has several implications. - Having not actually tested this in my own repos, take my insight with the appropriate grain of salt.
- shane_kerns 3y agoWould love to see a 3 way comparison between Pijul, Fossil and Git
- Aachen 3y agoThe submitted website says they're explicitly against 3-ways. Either drop one or add a fourth!
- t43562 3y agoI used darcs before git and it was very nice - the first distributed RCS I'd ever used. I believe pijul is a follow-on to that so it should be great. Later on I used Mercurial and it was very easy with a great GUI and it felt safe. git is like shaving with a straight shaving razor - alarming until you've developed your set of frequently used commands and ways to stay out of trouble. Even I have to use git because who uses anything else? Every project that I know that used Mercurial dropped it in the hope of getting more contributions. We have all rushed like Lemmings into Github - now owned by those nice people at Microsoft - who have used it to automate our jobs with copilot. How ridiculous that Open Source has been embraced into the clutches of the Empire on such a scale! :-) I am joking but only a bit.
- Zambyte 3y ago> Even I have to use git because who uses anything else? Git compatibility is a great way around this problem. I have been enjoying Jujutsu lately.
- adastra22 3y agoNot really. The real innovation of a lot of these alternative DVCS systems is that they free the state of the source from being dependent on the history that got you there. Such that applying patches A & B in that order is the same as applying B' & A' -- it results in the same tree. Git, on the other hand, hashes the actual list of changes to the state identifier, which is why rebasing results in a different git hash id. So long as you require git compatibility, you're kinda stuck with git's view of what history looks like. Which is rather the point.
- Zambyte 3y agoJujutsu uses change IDs, which are an abstraction over commit IDs, that are stable over operations like rebasing.
- sunshowers 3y agoThat is definitely a tradeoff. On the other hand, the history of all human progress is a history of path dependence. Constraints spur creativity and Jujutsu works extremely well. (I've worked with the main author of Jujutsu before. Also, having worked on Mercurial for many years, I have my biases about how source control should work. Jujutsu's workflow is very similar to Mercurial's, with some rather stunning improvements on it.)
- tveita 3y agoThe front page could do with a simple example of a Pijul session to show how you would actually use it in practice. Maybe whatever would be the Pijul equivalent of a clone - branch - commit - push workflow.
- vim-guru 3y agoFunny timing of this post. This past weekend, I dedicated myself to creating a comprehensive set of tools for integrating Pijul seamlessly into Emacs. This includes collaboration features through org-mode, which I believe will be refreshing. I'm eager to share it with the community shortly. For fellow Emacs & Pijul enthusiasts, keep an eye out!
- magnio 3y agoFunny username :)
- vim-guru 3y agoNot intentional; I used vim 10 years ago, but have been an emacser with vim-bindings for the past 7 I guess :)
- WolfeReader 3y agoPersonally, I find it quite gratifying to see that a "Vim guru" is also an active Emacs supporter.
- hirvi74 3y agoThe only path to enlightenment is to use both.
- ecshafer 3y agoThat is the best set up imo. Vim keybindings and composability are great, but Emacs being built on Lisp is a super power.
- bbkane 3y agoIn a similar vein, it's been incredible to watch the Cambrian explosion of plugins since NeoVim introduced deep Lua integration and configurability.
- 3y ago
- conaclos 3y agoIs a git backend planned?
- devaiops9001 3y agoI like how Pijul has a math-centric approach under the hood. The name needs to be changed if they want to get traction.
- baq 3y agogit did quite well with its...
- Aachen 3y agoThat may be survivorship bias. How many TLA projects failed that we never heard of? Not to mention the number of times I've tried to do a web search on an ordinary English word because someone thought that was brilliant to use as a product name and it turns up nothing because they didn't get as popular as Git or didn't have other distinctive keywords to go along with it, such as when your query not only includes "bash" but also "variable" that is unlikely to occur in a dictionary entry about the verb to bash I'd be very surprised if there is no causal relationship between names and the chances of success, all else being equal, and the devil is in the "all else". Evidently this is not a problem with a big enough marketing budget (think Teams and Meet), but without that it may be much more economical and practical to think of a useful name
- ZoomZoomZoom 3y agoJust to provide a counterpoint: The name is great! Very memorable and original. Much better than your regular plooper, vndl or dabix.
- goku12 3y agoPijul also turns up easily on web searches, despite there being a bird with that name.
- samatman 3y agoThey tried that actually. It was traumatic for everyone involved. It's a pretty weird word for English-speakers, no argument from me there. I don't think I can explain why it's weird, but it is. I don't think that's even in the top five barriers to adoption though.
- systems 3y agopijul seem to be written in rust, no one is mentioning it yet, so i though i would also because the language a project is written in, is one of the first things i like to check
- djha-skin 3y agoI'll be very interested in a usage report from somebody. How's it been like using this tool? Is there an email workflow I can use like git's? I feel like an email workflow could really help with adoption because it would mean that I wouldn't need a third party website to rely on for distribution.
- dahart 3y agoHey what does this item in the FAQ mean? > Do files merged by Pijul always have the correct semantic? > No. Semantics depends on the particular language you’re using, and Pijul doesn’t know about them. That makes it sounds like Pijul might sometimes merge two functionally correct versions of a file into an unfunctional, incorrect one? Is this referring to a problem git and other merge tools have as well, or is it unique to Pijul and a result of being so good at merging without conflicts that it sometimes lets through semantic conflicts?
- LeonidasXIV 3y agoYes of course this can happen in git as well, as it doesn't know the semantics of the changes it is merging, it only knows about textual conflicts. But if a change applies cleanly it doesn't mean that it necessarily also works, because the other branch might've changed the program logic. It doesn't happen very often, but it is still worth running integration tests after a merge even if both branches were passing tests on their own.
- magnio 3y agoAll version control tools have the same problem since AFAIK none of them care about the semantics of the program being version-controlled (except Unison). For example, in file foo.js you export the function foo. Now, if you delete the function foo, while your colleague import it into bar.js, the resultant changes are consistent, but the program is now functionally broken.
- riffraff 3y agomonticello[0] cares about semantics too! Tho I guess it cheats existing in an image-based world (I have never used it, it's just something stuck in my memory from many years ago). [0] https://wiki.squeak.org/squeak/1287 https://wiki.squeak.org/squeak/1287
- gmueckl 3y agoPlsstic's diff tool is also centered around syntactic units of the programming language rather than stupidly scanning for line breaks, if it recognizes the language.
- aezart 3y agoAs a left-handed person, that name is a nightmare to type.
- goku12 3y agoThat's what aliases are for. Regardless, I'm surprised that you even notice which hand you're typing with. For example, the word 'regardless' is mostly on my left hand and I'm right handed. But I wouldn't have noticed it if I didn't go looking for such words.
- samatman 3y agoAs a left handed person, I had not even noticed that pijul is typed with the right hand. As a touch typist, now that you've brought it to my attention, it's a pretty fluent run, actually. I type it 3-2-1-2-3, and back on the home row it is, the last key is in the rest point for that finger.
- Karellen 3y agoMissing FAQ: Is the "j" in Pijul hard or soft?
- 1oooqooq 3y agoIt's just pronounced "j". as the "g" in gif.
- FrancoisBosun 3y agoI logged in just to upvote this! Got a good chuckle out of me :)
- philwelch 3y agoThat’s not even an exhaustive set of possibilities.
- Aachen 3y agoIf you ask the waiter if they've got cauliflower or broccoli, I'm sure s/he'll still reply if all they've got is carrots, without being exhaustive
- ZoomZoomZoom 3y agoDon't know what hard or soft supposed to mean in a hypothetically ambiguous context, but the `j` here is obviously a Voiceless velar fricative (`x` in IPA). Think loch (Scott.), Χάρων (Gr.), joven (Sp.), хлопець (Ukr.) https://en.wikipedia.org/wiki/Voiceless_velar_fricative https://en.wikipedia.org/wiki/Voiceless_velar_fricative
- Karellen 3y ago~~"obviously"? Why?~~ aha! see edit 2 That pronunciation had temporarily escaped me. I was trying to decide between a voiced postalveolar affricate d͡ʒ (hard) or voiced palatal approximant j (soft). https://en.wikipedia.org/wiki/Voiced_postalveolar_affricate https://en.wikipedia.org/wiki/Voiced_postalveolar_affricate https://en.wikipedia.org/wiki/Voiced_palatal_approximant https://en.wikipedia.org/wiki/Voiced_palatal_approximant Edit: "hard" and "soft" seemed like the most logical way to describe what I thought was a dichotomy, particularly as it's also often used to distinguish between the voicings of "c" and "g". Edit 2: Just read the whole FAQ (rather than searching for "pronunciation" or related terms), and noticed the "Where does the name come from?" entry, which mentions the Mexican origin, which is why "x" is "obviously" correct.
- zck 3y ago> However, channels are different from Git branches, and do not serve the same purpose. In Pijul, independent changes commute, which means that in many cases where branches are used in Git, there is no need to create a channel in Pijul. I've never understood this. AFAIK, the only use case I've ever seen for git branches is "I have some code, but don't want it going live yet". Maybe it's a WIP demo, maybe you want someone else's eyes on it, maybe you just want to back your current state up on a remote server because your laptop is going to explode. Am I misunderstanding, and Pijul manages that without channels? Or is there a common case git branches are used that I missed?
- jph 3y agoA common case for git branches is long-life versions. For example, one git branch can be for version 1.0 and one git branch can be for version 2.0. This can be good for major upgrades, as well as for site-specific installations, as well as for regulated industries that need to audit specific versions.
- zck 3y agoSo we have a git branch v1, and a git branch v2, and sometimes we pull commits into both, and other times just one. How does pijul manage that without using channels?
- IlliOnato 3y agoI think the most common use for git branches is topic branches. Independent lines of development you are not ready to share with your team, or your team with the rest of the company, or commit to production. I don't see how Pijul features can remove the need for such lines of development. I also don't see how it matters whether a branch is long-lived or not. What Pijul may help with is a (broken, IMHO) workflow of some Git projects where the long-standing branches are constantly rebased. This workflow is bad, but having branches in Git does not force you to (mis)use rebase. I am not saying anything against Pijul, and maybe there is a better way than branches to manage multiple lines of development, but I'd like it to be explained. So far I cannot guess what it might be.
- 3y ago
- keybored 3y agoSo Pijul is patch-based. And not in the boring implementation-sense of storing changes as a series of patches. In the interesting sense that patches can be ordered in more arbitrary ways. On the other hand Git is snapshot-based. And Git was built for the Linux Kernel (specifically from the perspective of the lead maintainer). But my impression from the outside is that the Linux Kernel development is very “patch-based”. First of all in the sense of sending patches via email. But also in the sense that these patches can be applied to multiple trees (not just the Linus tree) and different subsystems have to cherry-pick commits (i.e. picking a commit and applying it as a patch, creating a new commit somewhere else). And it seems that people are concerned about tracking what patches are where, what commit (which can correspond to many commits according to cherry-picks) fixes whatever commit. The people behind Patchwork (a tool for maintainers which tracks patch series) is concerned about being able to track patches; the usual `git patch-id`, naming heuristics, etc. does not seem good enough. And as patches go through different contributors and maintainers they accumulate trailers in the form of signed-off-by and things like that. Even non-trailer (not key-value line) changelogs like: `[<initials>: fixed typo/ fixed off by one]`. And if the change is in the code then the patch content changes (not just the commit message). The Git project is also pretty patch-based in its development. Even for those who only cares about the maintainer tree: these patches apply to this other in-flight patch series; this diff here can be applied on top of your pending patch series; this patch series is from our ongoing work at Gitlab (company); I’m resending this patch series that X did three months ago but seemed to have abandoned; etc.
- danShumway 3y agoGenuine question, I have no opinion on this: My understanding is that a big part of the reason that Git is snapshot based is for reliability and for ease of checkout -- being snapshot based means Git doesn't need to replay commits every time you check things out. That likely comes with some downsides (cherry-picking does come to mind, yes), but also seems like some serious upsides, one of the biggest one being that simplicity. It's relatively easy for me to reason about what Git is doing under the hood. I like that I'm seeing that Pijul's patch operations are associative, I like at first glance what I'm seeing it say about merges, but it's not making it clear to me what the downsides are. Is the idea that arbitrary checkouts take longer, but that's generally fine since people don't do them very often? Or am I over-estimating how much complexity/performance costs that building a vcs like this would incur?
- Communitivity 3y agoI have used professionally Darcs, Mercurial, Subversion, and Git. I love distributed version control systems, and I love Git. However, Pijul looks interesting, nice work! Pijul has a number of stated strengths over Git, and looks like the version history is implemented as a CRDT from my first impression. Some of the statements make me wonder how many conflicts occur in real use. If they are equal to or less than the number it produces, great. If more than what Git produces, that's a barrier to adoption, as merge conflicts are one of the biggest pains when using Git. For me though what appears one of its biggest strengths (commutative workflow) is also its biggest drawbacks. There are so many teams that are trained in git workflow and are used to it, that getting them to switch to a completely different style of workflow in sufficient numbers will take years. Git compatibility is a key missing feature. Git had this with Subversion, and I think it's a big reason why Git won over many of the Subversion crowd.
- samatman 3y agoThe basic premise of Pijul is that the way they model changes leads to better merges, fewer conflicts, and (crucially) no cases of bad merges. Git can complete merges and do it incorrectly. https://pijul.org/manual/theory.html https://pijul.org/manual/theory.html This means that in some cases, Pijul will correctly merge where any of the git merge strategies would create a conflict. It also means that in some other (rarer) cases, Pijul will generate a conflict where git would not: git would guess, in effect, and either get it right or get it wrong. I consider both of these things to resolve in Pijul's favor. The Pijul model also means that conflicts preserve some crucial state which can be used to resolve the merge. A conflict is modeled as a specific data structure, not as special syntax intruded into the source file. One example of this is that conflicts can in some circumstance be resolved by applying more patches, because the conflict is metadata about the file, it isn't data in the file which screws with subsequent state changes.
- hosh 3y agoWhat I am excited about Pijul is being able to maintain a personal codebase that can accept changes from multiple upstreams. I’m not looking at commercial teams as much as homelabs or local-first environments.
- IshKebab 3y agoI'm watching this (and Jujitsu, Sapling, etc.) with interest, but I wish there was more focus on Git's real weak areas. Yes it sometimes makes merge conflicts more difficult than it could, but you can generally deal with that. The bigger problems are: * Poor support for large/binary files. LFS is bare-minimum proof of concept. * Poor support for large projects. Big monorepo support is definitely getting better thanks to Microsoft. Submodules are a disaster though. How does Pijul support large files and large projects?
- pmeunier 3y ago- Large/binary files: Pijul splits patches into operations + contents. You can download a patch saying "I added 1Tb there" without downloading any single byte of the 1Tb. No need to add any extra feature. - Large projects: Pijul solves that easily using commutativity, you can work on partial repos natively, and your changes will commute with changes on other parts of the monorepo.
- IshKebab 3y ago> No need to add any extra feature. Well that's the building blocks, but Git can do that through blob filters and whatnot. It's a necessary foundation but not a complete feature. You need ways of recording which blobs should be fetched eagerly, which should be fetched on demand, maybe a way to indicate where to get the data (you might want a central store for big files like LFS). > you can work on partial repos natively That's very good. Does it have anything like submodules or subtrees? I kind of think they are a bad idea in general but people do use them and they can be useful in very niche cases. From the sounds of the patch-based system I guess you could do subtrees quite elegantly? Can the patches be given a "base directory"? I don't want to seem like all this stuff should be done immediately but it does feel like these are things that kind of need to be integrated from the start to work properly, unlike in Git where they've been tacked on badly.
- deleted 3y ago[deleted]
- nrabulinski 3y agoI tried using pijul as the main VCS for my projects I really did and the fundamentals are awesome, but last time I used it the UX was pretty terrible. The easiest and most immediate thing that’d address my issues would be git status-esque command, which has been in development for quite some time, but still hasn’t landed last time I checked. I wish pmeunier all the best and I’m glad to try out pijul again once it’s a bit friendlier.
- pmeunier 3y agowe have `pijul diff -sU`, which is similar to `git status`. Also, feel free to contribute!
- woadwarrior01 3y agoIIUC, Pijul has all the good parts of Darcs, with the exponential merge issue[1] resolved. [1]: https://darcs.net/FAQ/Performance#is-the-exponential-merge-problem-fixed-yet https://darcs.net/FAQ/Performance#is-the-exponential-merge-p...
- Riyadh95 3y agoAwww That's Grear!!!
- WolfeReader 3y agoDoes Pijul handle branches better than Darcs? I _love_ using Darcs but I had to stop because there was no good way for my teammates to see my new branches (really separate repos) unless I told them myself.
- WolfeReader 3y agoGotta say, I don't see anything about it in their site's "Documentation" link. Unless I hear different, I don't think I'm interested.
- WolfeReader 3y agoDisregard, it seems that "channels" may be what I'm looking for here.
- pmeunier 3y ago`pijul fork`. There you go, I wrote an entire key-value store just to get that to work. It turned out to be faster than all others, but that wasn't intentional.
- WolfeReader 3y agoNice!
- Mortiffer 3y agoThank you for innovation that could free us from git
- crabbone 3y agoI don't want this to be interpreted as a negative comment about Pijul: I didn't try it, and don't want to judge. My question is: what is the motivation for making distributed VCS? Over the entire lifespan of Git the number of times I had more than one remote... I can probably count on my fingers. And I've been in infra / ops for the better part of my career. And, all those times were exceptions. I'd do it to fix something, or to move things around one time, and then remove the other remote. Other times it was my hobby projects I shared with someone in some weird way. Most developers who aren't in infra will never see a second remote in their repositories even once in their career. It seems like developing this functionality adds a significant overhead both in terms of development effort and learning effort on the part of the user. So... why?
- zemo 3y ago> what is the motivation for making distributed VCS? it depends on if you're asking about the motivations for distributed version control for linux kernel development in 2005 or the motivations for distributed version control today. git predates AWS and predates the state of the industry being that it's very easy and cost-effective for people to make central servers and web apps and things of that nature. My understanding is that "emailing a patch to a mailing list" was a more reasonable workflow then, since it piggy-backed off of people's email hosting providers (which, at that time, wasn't even "everyone using gmail", since back when git was created, gmail was invite-only; git predates gmail having open signups). Plus Subversion's branching model wasn't particularly great, so having different people work on things on different branches and giving them feedback and merging the branches when they were ready wasn't really a great experience. The distributed nature of the version-control system facilitates branches, since a branch and a copy of the repo somewhere else are abstractly the same thing. Practically speaking, people don't push and pull code between their workstations and the network topologies are typically centralized in nature, but on a data level the distributed model is dual to the branching model, and the branching model is the thing that people actually care about. Although I _do_ think it's pretty neat that you can use a thumb drive or NAS as a remote instead of needing a server, it's probably not a core use-case for most people and most projects.
- 3y ago
- zokier 3y agoI feel I'm missing something; for a version control system, you'd think managing different versions would be kinda central but in pijul that seems more like an afterthought. If I'm reading correctly you could use 'channels' same way as you use git tags, but that doesn't seem to be happening in practice. For example I look at 'sanakirja' project. The current version is 1.4.1 and the previous version was 1.4.0, and the version before that was 1.3.3: https://crates.io/crates/sanakirja/versions https://crates.io/crates/sanakirja/versions but if I look at the repository, there is no way to see any of that? https://nest.pijul.com/pijul/sanakirja https://nest.pijul.com/pijul/sanakirja There is "Tags" tab which is empty, and channel selection drop-down that has only "main" channel. So if I want to browse code at version 1.3.3, or see the difference between 1.3.3 and 1.4.0, or even just see what versions there are, how would I do that? To me those seem like very elementary questions, and yet reading through the manual I can find no hints toward this direction. There is a FAQ entry that seems relevant: > Is it possible to refer to a specific version? > Excellent question. Since Pijul operates on patches rather than snapshots, versions are essentially unordered sets of patches. How do we communicate a specific version number to one another? We solve this by abusing elliptic curve cryptography primitives. But its not clear at all how those "version identifiers" can be used or indeed if they are even implemented at all yet? At least based on the manual, no commands seem to take "version identifier" as argument, nor can I see them anywhere in Nest web UI.
- zokier 3y agoOh, apparently there is `pijul tag` command that might do something relevant here? https://nest.pijul.com/pijul/pijul:main/QL6K2ZM35B3NI.JIAAA https://nest.pijul.com/pijul/pijul:main/QL6K2ZM35B3NI.JIAAA but the docs do not say anything about that, so it remains a mystery. also its still weird that their own projects do not use those tags, or is it just that the web UI isn't showing them properly?
- pmeunier 3y agoOops, don't look at what we do! These repos have been used for dogfooding and bootstrapping extensively, they have the worst structures and aren't good examples of nice, clean workflows. The tool isn't really "experimental" anymore, its repos are still used for heavy experiments. > But its not clear at all how those "version identifiers" can be used or indeed if they are even implemented at all yet? At least based on the manual, no commands seem to take "version identifier" as argument, nor can I see them anywhere in Nest web UI. `pijul log --state` does that, and various commands (tags, fork) do it as well. Tags are due for a redesign, since they can be made much more efficient with a really cool new design, and make Pijul a perfect hybrid between patches and snapshots.
- mdaniel 3y agoheh, curl https://nest.pijul.com/pijul/pijul/changes https://nest.pijul.com/pijul/pijul/changes | grep -i "fixing conflicts" (e.g. https://nest.pijul.com/pijul/pijul/changes/44SHUW5W6RMWYDF2RKYB77S3VVFXT4ALRXKRXGKBQTONXTQQZBQAC https://nest.pijul.com/pijul/pijul/changes/44SHUW5W6RMWYDF2R... )
- dang 3y agoThe current submission counts as a dupe since this topic had significant attention less than a year ago: Pijul: Version-Control Post-Git [video] - https://news.ycombinator.com/item?id=37094599 https://news.ycombinator.com/item?id=37094599 - Aug 2023 (163 comments) Other past threads: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=%22Pijul%22%20comments%3E0&sort=byDate&type=story https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...