> I believe the problem comes from a conceptual mismatch of what a timezone object should be. There seem to be two commonly understood meanings of timezone whi

> I believe the problem comes from a conceptual mismatch of what a timezone object should be. There seem to be two commonly understood meanings of timezone which are confused in UIs and APIs: a geographical area which follows a particular winter and summertime regime over the year; and a particular offset from UTC like GMT or BST. I've seen a lot of bad design rooted in this confusion.