SaaSHub helps you find the best software and product alternatives Learn more →
Beagle Alternatives
Similar projects and alternatives to beagle
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
libcurl
A command line tool and library for transferring data with URL syntax, supporting DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS, MQTT, MQTTS, POP3, POP3S, RTSP, SCP, SFTP, SMB, SMBS, SMTP, SMTPS, TELNET, TFTP, WS and WSS. libcurl offers a myriad of powerful features
-
-
-
-
-
-
-
-
-
-
sem
Semantic version control => entity-level diffs, blame, and impact analysis on top of git. 26 languages via tree-sitter. Built for coding agents.
-
weave
Entity-level git merge driver. Resolves false conflicts git invents when independent agents edit the same file. ~95% reduction vs. line-based merge. (by Ataraxy-Labs)
-
-
-
MKS-DLC32
MKS DLC32 motherboard kit, which is an offline engraving master control kit developed for desktop engraving machines. The hardware is equipped with a 32-bit high-speed ESP32 module, integrated WIFI function, and directly drives a 3.5-inch touch color screen; it can realize fast engraving and WEB web pages. Control, mobile phone APP control and other functions.
-
-
beagle discussion
beagle reviews and mentions
-
Interleaved Deltas
Virtually any merge algo is a weave in a trench coat, so yes, weaves always return. In Beagle, that is more explicit: diff, merge, blame are all weave based
https://github.com/gritzko/beagle/blob/main/graf/WEAVE.h
-
Sp.h is the standard library that C deserves
I use a C dialect with (ptr,ptr) slices and (ptr,ptr,ptr,ptr) buffers. Effectively a different programming language, still uses standard C compiler.
https://github.com/gritzko/libabc
In this day and age, the top problem is Claude bringing lots and lots of bad C into the code base. Takes a weekend to clear the week's mess.
https://github.com/gritzko/beagle
In a cleared codebase though all the usual C memory bugs are virtually non-existant. When did I see core dump last time? I do not remember. Thus feel no urge to use Zig or Rust.
-
I Will Not Add Query Strings to Your URLs
how does adding the word blob in the url help with that?
i don't think it makes a difference here.
in fact compare these urls:
https://github.com/gritzko/beagle/blob/a7e172/VERBS.md
https://github.com/gritzko/beagle/raw/a7e172/VERBS.md
https://github.com/gritzko/beagle/commit/a7e172/VERBS.md
turns out that "blob", "raw" and "commit" have nothing to do with the hash itself, but are functions to describe how the object in question is to be presented. so what i said above about blob being redundant is false, the problem is rather that it is in a weird place. it should be at the end, like a kind of extension because it signifies the format of the output. except i think putting it at the end makes handling relative paths more difficult as it would have to be appended to every link to other files.
the roxen webserver has an interesting solution for that. they call it prestates and it's placed at the beginning of a url: https://github.com/(commit)/gritzko/beagle/a7e172/VERBS.md . it sets the format value visually apart, and you could have multiple prestate values separated by a comma. i have used that feature extensively on my own sites. i even expanded on the concept in custom modules.
- Spot – Git repo code search, replace, diff and merge
-
Lies I was told about collaborative editing, Part 2: Why we don't use Yjs
One way to minimize impedance mismatch is to work with DOM-like or JSON-like structures mostly immune to transient bugs, which I am doing currently in the librdx project. It has full-CRDT RDX format[1] and essentially-JSON BASON[2] format. It does not solve all the problems, more like the set of problems is different. On the good side, it is really difficult to break. On the bad side, it lacks some of the rigor (esp BASON) that mature CRDT models have. But, those models are way more complex and, most likely, will have mismatching bugs in different implementations. No free lunch.
[1]: https://github.com/gritzko/librdx/tree/master/rdx
- Beagle, a source code management system that stores AST trees
-
Sem – Semantic version control. Entity-level diffs on top of Git
Was "sem" named "graft" last week and "got" a week before that? Everyone is vibing so hard it is difficult to keep track of things.
Still, my two cents: Beagle the AST-level version control system, experimental
https://github.com/gritzko/librdx/tree/master/be#readme
It genuinely stores AST trees in (virtually any) key-value database (RocksDB at the moment). In fact, it is a versioned database for the code with very open format and complete freedom to build on top of it.
-
Ki Editor
I am working on AST based revision control. I have a stack of ideas on how to achieve the same Ctrl+W effect with commits/diffs/cherry-picks. All still in flux. In case you have insights, please share!
[1]: https://github.com/gritzko/librdx/tree/master/be#readme
-
Weave – A language aware merge algorithm based on entities
Beagle is a revision control system like that https://github.com/gritzko/librdx/be
- Beagle SCM: repos, branches, waypoints and milestones
-
A note from our sponsor - SaaSHub
www.saashub.com | 9 Jun 2026
Stats
gritzko/beagle is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of beagle is C.