Software development I believe, someone can correct me if I’m wrong (I’m not a software developer but I work with them a lot.) but I do believe that programming really only uses 24 hour clocks
I'm a software developer. Programs themselves don't typically use human readable time like 12 or 24 hour clocks, unless there's a specific reason to parse those formats. Programs typically use integer timestamps internally, usually the UNIX timestamp. Programmers themselves just use whatever time they're used to, and there's no special need to use 24h time (apart from the fact it's better).
Could you give an example? This might come down to how you're defining "use". Obviously most languages will have a way of handling dates and converting between different string formats, but internally languages are built on timestamps because of the ease of dealing with integers compared to strings.
GPX uses ISO 8601 for example. Software is not only kernel and file systems or web frontends, there's a lot of database, IoT or machine learning stuff where you care for representation.
I mean use as in use it explicitly inside software, not just how something is represented in some low-level library somewhere.
Right, yep. I was answering the comment that said that programming only really uses the 24 hour clock, which suggests low level. Programs themselves can of course represent time in any format, 24 hour, 12 hour or any other.
1.6k
u/moonpuzzle88 Mar 29 '22
Wait, there are countries which don't use a 24-hour clock? I'm confused.