3 ms·

I love Fossil and I use it for my projects. I understand why it isn't for everyone, but considering I am the sole developer on the stuff I make (and I agree wit

by bigstrat2003 13d ago

I love Fossil and I use it for my projects. I understand why it isn't for everyone, but considering I am the sole developer on the stuff I make (and I agree with Dr. Hipp about the drawbacks of rebase), it's perfect for my needs. Lightweight, has its own integrated web server and forge features should I need them, and it's dead easy to use. It isn't the one VCS to rule them all (no such thing exists, really), but I do encourage people to check it out because they might fall in love like I did.

theamk 13d ago
What happens if you make a mistake while committing - maybe forget the file, or commit wrong one? Fossil has no way to fix it, by design, and I find it an absolute showstopper. I do stupid mistakes all the time, and I am so glad that gits lets me fix those.
- hju22_-3 13d ago
  It does: https://fossil-scm.org/home/doc/tip/www/shunning.wiki https://fossil-scm.org/home/doc/tip/www/shunning.wiki.
  - theamk 13d ago
    "Fossil purposely makes it difficult for users to delete content." Those operations are explicitly declared special, not something you do many times per day because you had a typo in your print statement. I guess technically you can do it often, but the tooling does not make it easy at all, and you are going against program's recommended best practices.
- sgbeal 13d ago
  > 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.
  - theamk 13d ago
    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.
- grebc 13d ago
  Who cares. Add another commit is the answer.

theamk 13d ago

What happens if you make a mistake while committing - maybe forget the file, or commit wrong one? Fossil has no way to fix it, by design, and I find it an absolute showstopper. I do stupid mistakes all the time, and I am so glad that gits lets me fix those.

hju22_-3 13d ago
It does: https://fossil-scm.org/home/doc/tip/www/shunning.wiki https://fossil-scm.org/home/doc/tip/www/shunning.wiki.
- theamk 13d ago
  "Fossil purposely makes it difficult for users to delete content." Those operations are explicitly declared special, not something you do many times per day because you had a typo in your print statement. I guess technically you can do it often, but the tooling does not make it easy at all, and you are going against program's recommended best practices.
sgbeal 13d ago
> 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.
- theamk 13d ago
  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.
grebc 13d ago
Who cares. Add another commit is the answer.