> As an expansion on that, as far as I know there's only one implementation of Fossil.
That's is, since only recently, no longer strictly true: the age-old libfossil recently got client sync support, so is now (aside from _serving_ repos) essentially a standalone impl (its own developer still uses fossil(1) stash, patch, and diff -tk features, but otherwise uses libfossil's counterparts).
Also, Dan Mestas has <https://github.com/danmestas/go-libfossil>, a Go library for working and fossil, and he is also working on <https://zeitforge.app/>, a clean-room impl. of fossil (whereas libfossil is largely ported directly from fossil(1)) which even goes so far as to _not_ use an sqlite database for its file storage.
Dan Mestas and Dan Shearer are working on finalizing RFCs for fossil's sync protocol and artifact format, and zeitforge is created by carefully managing LLMs which are reading that draft (but not the source code of libfossil or fossil).
I personally have been using `go-libfossil` in a project! It's got some sharp edges but insanely useful in avoiding CGO and using fossil at the same time
> What happens if you make a mistake while committing - maybe forget the file, or commit wrong one?
Then you have proven that you are human.
> Fossil has no way to fix it, by design,
As an 18-year-long contributor to fossil i can assure you that this is absolutely not true. Fossil can amend any checkin and it can move checkins to other branches. Go to sqlite.org/src/timeline?r=mistake to see many examples of where human failing has been both demonstrated and accounted for without breaking anything.
14 "mistakes" in the entire 2025. I am probably making that many per week? Not to mention committing the intentionally broken stuff, with the expectation that I'll come back and amend if I decided it should go to main.
> IMHO the best and most relevant part of fossil these days is the ticket system, which is in every single way almost completely ideal for coding agents.
Funnily enough, that's collectively fossil's developers' least-favorite part. We make no secret about not liking the ticket system, and we only use it when we need to record a certain ticket for posterity's sake. Aside from that, we use the forum for all ticket-like traffic.
> Since the whole tracker is just a thin front on sqlite ...
> If you mean your skills stagnated 10+ years ago and have not advanced since then, then... yeah, you might be the only one ;).
Unfortunately, definitely not. There are lots of people still doing the same as they did a decade ago who have learned very little. Very often the people who knew very little to start with.
My "10+ years" was not referring to any specific milestone. It was referring to the general flow of time. It's been 10 years since 2016, twenty since 2006, and more than 40 since writing my first program. Lots has changed every 10 years in that period, both in my skills and the environments i program in, but shell/emacs/makefile remains a staple of that process.
Ah, well the question you were answering spoke of 2021. It's not about not changing your practices in a decade but about LLMs. Apparently you dodged both questions by neither referring to 2021 nor to the thing that became somewhat usable in 2021 xD
Any half decent IDE will change them automatically for you, no need to chase them down. Just look at the git diff if you want to see where things changed.
> Any half decent IDE will change them automatically for you, no need to chase them down
It's long been my experience that that only works with high-level languages (specifically, those with bytecode), not C (especially once symbols are generated from macros). (OTOH, i've not touched an IDE in well more than 10 years.)
Also, it's long been my experience that any half-decent IDE is still a pale shadow of Emacs.
Yeah this is a very very common and fundamental operation in programming. Always use the “refactor” tool in your IDE instead of trying to change every instance of a variable name by hand.
It’s like using a linter: you do it because it’s the right thing to do and doing it without the tool confers no benefit and is prone to error.
> i demonstrated replacing _all_of them at once, not replacing them each by hand.
Not really, that is search and replace. IDE's do typesafe refactoring. If you change the Find method in class A, you should only change occurences of x.foo(), where x has type A. You shouldn't accidentally change all B.find()'s.
That is my advice for everyone completing their first Python tutorial: learn a typed language next if you aspire to do serious work. It also saves you writing many manual tests that you had to make otherwise, as the compiler makes that superfluous. Plus your IDE becomes a superpower.
> My first attempt at restoring 1991 Learning Company Spellbound for DOS for my children is dubious. Despite being stored nowhere near magnetic sources, there are read errors on the 3.5 inch floppies and Linux could not mount them.
FWIW, it's long been my experience that floppies (like CDs and DVDs) have a half-life and they degrade quickly upon reaching it. You'd have been lucky to be able to recover those in 2001. Now? If at all, only high-end forensic tools could recover them.
> You'd have been lucky to be able to recover those in 2001.
2001 might be a stretch but indeed they do degrade badly. During Covid I was locked down, by a stroke of bad luck, alone, 2000 kilometers away from my wife and young daughter... In the house were I grew up. My old Commodore 128 was still in the attic and I dug it out, cleaned it, cleaned (and greased) the disk drive and tried to read my 5"1/4 floppy disks.
I'd say I got about 50% success: one disk out of two was already unreadable.
One could see it as "50% success rate after 35+ years is quite good" but I fear that if I were to try now, many more would fail.
I took the opportunity to make a copy of the game Commando (which has an incredible chiptune by Rob Hubbard) on two NOS (new old stock) 5"1/4 floppies. For thankfully I had a copy a Fast Hack'em that'd still boot.
Having real time capsule stuff, re-using data from old floppies that haven't been archived since decades, is becoming near impossible.
In my experience CDs and DVDs I burned myself have a lifespan even shorter than floppies. Most of the CDs I burned in the late 90s/early 2000s are already unreadable.
> In my experience CDs and DVDs I burned myself have a lifespan even shorter than floppies. Most of the CDs I burned in the late 90s/early 2000s are already unreadable.
Similar here: CDs and DVDs burned from 2000-2006 or so were, without exception, illegible by 2015. It's sickening.
> only interact with people using an official email address.
And then google whether the domain is associated with phishing attempts. i've been targeted several times recently by folks with "official" email addresses but whose domains are (per google) strongly associated with phishing.
That's is, since only recently, no longer strictly true: the age-old libfossil recently got client sync support, so is now (aside from _serving_ repos) essentially a standalone impl (its own developer still uses fossil(1) stash, patch, and diff -tk features, but otherwise uses libfossil's counterparts).
Also, Dan Mestas has <https://github.com/danmestas/go-libfossil>, a Go library for working and fossil, and he is also working on <https://zeitforge.app/>, a clean-room impl. of fossil (whereas libfossil is largely ported directly from fossil(1)) which even goes so far as to _not_ use an sqlite database for its file storage.
Dan Mestas and Dan Shearer are working on finalizing RFCs for fossil's sync protocol and artifact format, and zeitforge is created by carefully managing LLMs which are reading that draft (but not the source code of libfossil or fossil).