You know, I've never sat down and worked out the sum of all differences, but I'm a tcsh-er of long standing since I grew up in the University of California and everything on BSD/386 was /bin/csh, so when I graduated and ran my own systems, I switched to tcsh.
Mac OS X Panther just switched the default to bash, also.
Near as I can determine from the times I've been forced to use it, bash has csh job control, but no csh scripting or shell-builtins (which is what drives me wild) -- you use ksh or sh syntax for those. I'm pretty sure it has the same features as modern tcsh including filec, history and vikeys, but I don't know how to turn them on and I don't care
The shells are equivalently functional as far as I know, it's just what you're used to. If you have a csh background, you'll prefer tcsh; if you have a ksh or (shiver) sh background, you'll want bash.
"you're a doctor.... and 27 years.... so...doctor + 27 years = HATORI SOHMA" - RoyalWing, when I was 27
"Al hail the forum editting Shooby! His vibes are law!" - Osaka-chan
I could still be champ, but I'd feel bad taking it away from one of the younger guys. - George Foreman