nightfader
Re:macOS Containers v0.0.1
on Tuesday September 26, 2023 @07:42AM (#37657841)
Homebrew is available for Linux as well since approx 3yrs now. I've been using it without issues https://docs.brew.sh/Homebrew-on-Linux
Re:Fossil versus Git
on Saturday September 23, 2023 @08:50AM (#37622804)
That's also why perforce is slow as heck unless you throw massive resources at it. I also work in the chip industry BTW.
Re:Fossil versus Git
on Saturday September 23, 2023 @08:47AM (#37622778)
Because git excels in relatively small size text files and patching and difficult. You can't binary blobs like jpegs, audio, video easily.
Re:Fossil versus Git
on Saturday September 23, 2023 @08:41AM (#37622743)
How is it not bad design? Let's say you are working in a team. Would you really want your colleagues spending a significant amount of time cloning your artifacts? Your comment is also not consistent with forgetting that one is not a developer. Even if it's my grandma, she's not gonna want to wait for 1hour to download a giant file from VC assuming she knows what a VC is.
Large blobs can go into versioned object storage like GCS or S3 etc
Re:Fossil versus Git
on Saturday September 23, 2023 @08:36AM (#37622724)
That's what object storage with versioning turned on is for e.g. GCS or S3
Re:Fossil versus Git
on Saturday September 23, 2023 @08:18AM (#37622620)
The whole point that git rejects large blobs is primarily because they don't belong in VCS. But for those who need large blobs there is git-lfs as the author mentioned. I don't see a problem with that approach because I personally don't like my git repos growing large after just a few commits which then takes up time for huge clones by other devs. This is the whole principle behind monorepos. If going the monorepo route it's in a teams or projects best interest by keeping the repo size small so new clone by newly onboarded devs or during a CI pipeline don't take forever.
Fossil is an all in one VCS with wiki, issues etc which I don't appreciate because for one it's not feature rich and for another it bloats the backups and restores. So I prefer gits Unix philosophy of doing one thing but doing it really well.
There are some philosophical amd usability differences between fossil and git too but in the grand scheme of things it doesn't matter when one has been using git for a long time. Fossil doesn't have an ecosystem either and making it work with CI CD is a pain because CD tools like agrocd or flux or CI tools like gitlab/gitbub/circle/travis CI systems don't work with fossil out of the box.