Generally I will use lists for fast and loose vectors, in unoptimized code, and tuples for more firmly "typed" data, or performance enhancements.
I don't need more and I don't need less: the two seem well-balanced for me.
As someone who abhorred Perl, Ruby looks a little frightening. Python looks and feels clean, especially for blocks of data.
In OO though, self.whatever appears more frequently than I'd like.
Pretty much yes. dicts are something completely separate from list-like types. Those should not be mixed.
lists and tuples depend on your preference really, but I appreciate them being available. There are many places where you want to pass an immutable sequence of objects and the list is just not right... Sure we could get rid of them, but what would be the gain there?