What are the actual use cases for rebasing? I've never had to use it, and I used git for a hackathon project with 3 of my friends. The hardest part was merge conflicts, but a good IDE takes care of those for you.
(This reflects my experience of working, possibly, you've had others).
On SVN, basically when everyone commits, everyone else merges what others commit. Multiple people generally work on the same branch. Translated into "industry", for example, making an house, that would mean that every day you download the house and that multiple parts of the house gets "updated", you've got 50% of a window, next day 60% of a window... and so on. Problem with this approach is "merging" when multiple people try to do work on the same stuff, for example, putting water pipes into walls. You end up with 40% of the pipe in a 50% wall, both are inherently merged into one another.
On Git, you're supposed to take every dev into its own branch. That means that I'm working on the pipes, for example, and another guy does the wall. Let's say I finish the pipes before the wall are. I install them. Then the guy that does the walls finishes. He rebases his wall into the house, and the wall is done. Then, the rebasing tries to install my pipes. If there is conflict between both, then a wall / pipe merge is there.
However, both the pipe, wall, and (hypothetical) merge are still there. If later, you need to add protection to the pipes, you can remove the pipes, add the protection, and put the pipes back. Same idea if I want to replace the pipe.
On SVN, all is merged, so way more difficult to rework.
When comparing IT to industry, I find that it reinvents the wheel, most of the time.
