0 views collected around this technical thread.
This article explains GMT, UTC, time zones, local time, and daylight‑saving time, outlines their effects on game server and client logic, presents three common handling strategies, lists typical bugs, and provides a detailed testing checklist for reliable time‑related features.
The International Earth Rotation Service’s decision to skip the 2024 leap second and ultimately abolish leap seconds by 2035 relieves programmers of complex time‑keeping hacks, as current NTP, PTP, and newer Windows systems can already handle adjustments while past leap seconds have repeatedly disrupted software.
This article explains why time‑zone consistency is crucial in games, illustrates common pitfalls with UTC and local times—including daylight‑saving effects—and provides best‑practice guidelines for storing timestamps in UTC, preserving zone information, and displaying user‑friendly times to avoid data errors and user confusion.
The article explains how the International Earth Rotation Service’s decision to cease adding leap seconds after 2035 will affect computer systems, recounts past leap‑second‑induced outages, and discusses the long‑term timing drift challenges programmers may face.
This article explores the origins of time measurement, the transition from astronomical clocks to atomic standards, how UTC and leap seconds are defined, and the technical mechanisms—especially NTP—that keep computers and devices precisely synchronized across the globe.
This article presents a straightforward Java solution that converts UTC timestamps to Beijing time by applying an 8‑hour offset and provides utility methods to retrieve the current week number, month, day, and year using the Calendar class.
The article explains the historical definition of the second, the concept of leap seconds, their impact on large‑scale IT systems, and details Alibaba's multi‑step approach of splitting the extra second into 86,400 parts to maintain accurate time synchronization across its infrastructure.