You can't see all 50-70 tabs on a normal 27" monitor; Chrome will squish them almost indefinitely, and Firefox forces a large minimum tab width that makes the tab bar scroll forever and then you forget half the tabs you have going and everything's bad. I tried to switch and stopped because of this. I'll hang on until ubo really stops working, I guess, and then try to figure something else out.
You might be unfair to yourself in the sense that not all hours are created equal; some hours were never going to be productive hours, and so if you can immerse yourself in a subject with some easy-to-watch videos, that might be better than trying to force productivity where none is available.
It was United or Alaska and was a few years back and fortunately it wasn't me on the plane, it was my wife - a big east coast storm and airport closures diverted her flight (along with a bunch of other flights).
I can only speak to the comparison with hg, but for large repos, git's performance is literally 10x better in our case (we have two parallel copies, one in hg and one in git, so as to smooth the transition to git). hg seems more usable, but certain decisions are poor (e.g. baking the branch name into each commit); overall I have no strong preference between the two except for the speed.
But the speed pretty much drowns out any other signal.
git's performance increase came around at the right time, too. Code bases were becoming bigger and bigger, and Agile's popularity preached a lot of branching. SVN branches were a full copy, making things way worse.
Yeah that had occurred to me. But I'd used TFS (which didn't have light-weight branches) with Agile-like development practices and it wasn't that big a deal. Maybe if the codebase was 10 or 20 times bigger it would've been.
