There is something strange that I cannot explain. When I use git I am comfortable rebasing quite a lot. When I use fossil I do not miss it at all.
Similarly, when I use go I do not miss generics despite using them quite a lot when they are available in other languages.
So based on this, I both agree and disagree with your complaint about fossil not having rebase.
However, one place where I disagree is that fossil is not just VCS for SQLite3. Its github in a single executable -- much more powerful and potentially much more important for the opensource community. In some dystopian future developers will be using fossil over tor.
It's possible that if I started using Fossil seriously I'd have the same feeling as you. However, when I browse SQLite3's history, I still see a branched model, not clean, linear history.
I can imagine that a VCS might make merging so painless that one might not miss rebasing, but I would still prefer rebasing.
Similarly, when I use go I do not miss generics despite using them quite a lot when they are available in other languages.
So based on this, I both agree and disagree with your complaint about fossil not having rebase.
However, one place where I disagree is that fossil is not just VCS for SQLite3. Its github in a single executable -- much more powerful and potentially much more important for the opensource community. In some dystopian future developers will be using fossil over tor.