bitkeeper
bazel-cache
| bitkeeper | bazel-cache | |
|---|---|---|
| 7 | 1 | |
| 378 | 0 | |
| 1.3% | - | |
| 0.0 | 0.0 | |
| over 1 year ago | about 2 years ago | |
| C | Starlark | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bitkeeper
- BitKeeper (GitHub Repository)
- master. that's is.
-
Is the name "Master" branch offensive?
This is not historically accurate, even in the narrow context of Git branch names. Git was initially written as a replacement for an old source control system named BitKeeper. BitKeeper had a concept of a “master repo” (the main remote repo); all other copies of the repo were “slave repos”. Example from the BitKeeper docs. Git inherited that naming convention.
- Casync – A Content-Addressable Data Synchronization Tool
-
Who gets to define what’s ‘racist?’
> git repositories don't have "slave" branches, just a "master' as in template or origin
That isn't true - master in git comes from master in BitKeeper which did have slave replicas.
https://github.com/bitkeeper-scm/bitkeeper/blob/master/doc/H...
-
The Perl Foundation is fragmenting over Code of Conduct enforcement
Git was originally based on Bitkeeper which uses the terminology in that way, for example: https://github.com/bitkeeper-scm/bitkeeper/blob/master/doc/HOWTO.ask
-
GitHub, f*ck your name change.
Git was created as a replacement for BitKeeper. BitKeeper does use the terminology master/slave. Thus, Git's use of master is in fact a reference to master/slave, not a master recording.
bazel-cache
-
Casync – A Content-Addressable Data Synchronization Tool
I did PoC experiments with compression, chunking, and IPFS here: https://github.com/SaveTheRbtz/bazel-cache
If you need a mature compression implementation for bazel I would recommend using recent bazel versions w/ gRPC-based bazel-remote: https://github.com/buchgr/bazel-remote
bazel nowadays supports end-to-end compression w/ `--experimental_remote_cache_compression`: https://github.com/bazelbuild/bazel/pull/14041
What are some alternatives?
Raku-Steering-Council - RSC Papers
desync - Alternative casync implementation
casync - Content-Addressable Data Synchronization Tool
bazel-remote - A remote cache for Bazel
zstd-seekable-format-go - Seekable ZSTD compression format implemented in Golang.
Bazel - a fast, scalable, multi-language and extensible build system
zstd - Zstandard - Fast real-time compression algorithm