This is a very interesting problem to tackle for all runtimes. In my experience, the main issues are: [1] How do we store the date / time fields in the databa

This is a very interesting problem to tackle for all runtimes. In my experience, the main issues are: [1] How do we store the date / time fields in the database tier [2] How do we display those fields to users in multiple time zones and cultures and gather validated input from those cultures [3] How do we do date / time math in a simple manner Issue [1] has implications for manipulating data directly (i.e. querying or reporting). Should the data be stored in UST or in some "local timeframe"? Issue [2] always seems to trip some developers: how do we render a time or date in a way that makes sense in a global world (i.e. "8/5/2014" vs. "5/8/2014" vs. "5-8-2014" or 3:26 PM vs 3:26 etc). Issue [3] is always a pain too, based on whatever decisions were made for [1] and [2]. Test of awesomeness: if your code works in Hebrew or Thai cultures!