On another note, how would you store your datetime in a database? If I understand correctly, we would need to save the location as well, so no real difference with a datetime+locale.
Am I missing something?
There is no need to store datetime or locale for the clock to work. The clock knows where you are, using your sys time, or GPS, and according to that it rotates the UTC layer that is represented in letters according to you location. This means the clock adjusts itself for you in order to give the right local-global (UTC) time mapping. And that's all done by the clock's algorithm that manages the rotation. The main reason I'm using letters instead of numbers for UTC is to distinguish between local and global hours, simply for better communication.
That's how it works :)
I have a feature for meeting planning. The clock then finds the best time for a meeting between the different location without the need to do any calculations on your end, or the other attendees' ends. With this feature, you can also choose the working hours availability. In the link above it shows the best time for a meeting between San Francisco, London, and Berlin for working availability between 8am and 7pm for everyone.
The idea is eliminate the calculations, and the confusing names of all time zones and daylight saving.