one reason I do not default to UTC or Zulu is that it doesn't account for daylight savings outside of manually adding 'UTC-5' or whatever zone you're in relative to daylight savings; so I just go with 24-hour notation with zone - 1414 EDT
To me, that's a reason in favor of Zulu time. Regardless of what time zone you're in, Zulu is always Zulu. (Even in Arizona.)
I agree, and I was hoping our state legislature would've see the writing on the wall and nix DST altogether; alas, (if you're a farmer that requires its use, by all means). until then, as I communicate with customers and contractors, I will give them the edge to simply not waste my time. I could only imagine the look I would get in setting a meeting or working group and using zulu convention - it's bad enough trying to herd cats for a meeting that couldve been an email.
I agree, and I was hoping our state legislature would've see the writing on the wall and nix DST altogether; alas, (if you're a farmer that requires its use, by all means). until then, as I communicate with customers and contractors, I will give them the edge to simply not waste my time. I could only imagine the look I would get in setting a meeting or working group and using zulu convention - it's bad enough trying to herd cats for a meeting that couldve been an email.
To be clear, I use 12-hour time and time zones FAR more often than Zulu time. Trying to get the average corporate drone to understand the concept of Zulu (let alone 24-hour format) is too much of a hurdle when you need to be efficient.
I'm just saying that Zulu is my personal preference, and if we were to implement OP's suggestion we should go all-in.
concur on al points.
I did use it operationally a lifetime ago - then it was GMT, but far easier to use since all satcom was based on GMT.. to hell with specific zones.
(post is archived)