I suppose I would choose Darcs & Pijul for version control systems to bit into Git hegemony (& if you prefer Git hegemony, don’t use proprietary code forges).

Additionally just the general vibes of IRC & XMPP for battle-tested chat applications that are lightweight for clients & servers alike. These are the kinds of tools your next community should be built on if you want to minimize resource usage (data plans, storage capacity, battery, CPU churn).

[–] uis@lemm.ee 1 points 6 months ago (1 children)

Darcs looks meh. Can't say anything about Pijul.

[–] toastal@lemmy.ml 1 points 6 months ago (1 children)

Looks meh why? Not interested it the Patch Theory for version control?

[–] uis@lemm.ee 2 points 6 months ago (1 children)

If all data is stored as patches, then no shallow cloning

[–] toastal@lemmy.ml 2 points 6 months ago* (last edited 6 months ago)

When a repository is cloned lazily, darcs adds an entry in _darcs/prefs/sources, so whenever you use a commands which needs to work with all the patches, darcs try to fetch the missing patches using the entries from the cache, since the original repository was added to sources, it is also added to the cache (since darcs relies on the source file to load the cache).

— https://darcs.net/Internals/CacheSystem#lazy-repositories-and-the-cache-system

You have all the code & fetch patches as needed. Not the same as a shallow clone, but if trying to not download the whole project history, this serves a smiliar goal.