What time is it... Really?


Recommended Posts

Many of you will soon be adjusting your clocks either one hour ahead or one hour back, depending on your location. And I am yet again reminded that no one really knows for sure what year it is.

Arguably the majority of the world recognizes it as the year 2,010 (2010). But this is completely based on the religious belief on when a single "religious being" lived & died. rolleyes.gif But this of course take out of count, the many years before this "believed" being lived or died.

Upon further reflection GMT (Greenwich Mean Time, established since 1884) has been replaced with UTC (Coordinated Universal Time, established since 1972). And it is worth noting that this UTC is based partly with UT (Universal Time), to which there are arguably 6 version of (UT1, UT0, UT1R, UT2, UT2R, UTC).

On top of all this... Not every county in the world adjust their clocks back & forth. Some keep a continued time all year around.

To make up for this lost time, we of course have added the idea of a "leap year" in which every 4 years we add an extra day. But if you do the math, that "leap year" does not fully account for every last second & as time continues to add... Those seconds become minutes, hours, days.... And of course, what about all the years before the calender included a "leap year"....

So what time is it? blink.gif

Link to comment
https://www.neowin.net/forum/topic/951474-what-time-is-it-really/
Share on other sites

Let's have some fun then

According to Judaism the year is 5771

The Christian calendar says it's 2010

And the Muslim calendar says it's 1431 AH

hmmmm, who to believe

I bet just about every major religion has it as a different year, this can be fun :)

*edit*

According to the Hindus it's 3102 BCE

I do software devt for an airline. The schedules are set in local time relative to each airport. Daily operational data are kept in UTC. Dispatchers can flip their displays between local and Zulu as needed. Before .NET 3.5 I had to code all the timezone translations manually. 3.5 introduced the TimeZone class which provided the necessary TZ conversions, but it still lacks a fully TZ-aware DateTime class. I had to write a custom class for that, to encapsulate the conversions and provide code for elapsed time calculations. Major PITA!

Arguably the majority of the world recognizes it as the year 2,010 (2010). But this is completely based on the religious belief on when a single "religious being" lived & died. rolleyes.gif But this of course take out of count, the many years before this "believed" being lived or died.

Actually, most historians today use C.E. (Common Era) and B.C.E (Before Common Era) for dates. These dates actually aren't based on Jesus birth, since he was actually born (using 'pivotal' dates, that is, dates attested to and confirmed from both Biblical and secular sources) in 2 B.C.E.

Using B.C. ('Before Christ') and A.D. (Anno Domini, Latin for 'Year of the Lord') are really not used anymore since they really aren't historically accurate. As far as Leap Years are concerned, there are other safetys imposed to keep run away leap years from messing us up. If you'll remember, 2000 was a leap year, but 1900 wasn't. Why? Because only years beginning centuries that are equally divisible by 4 are made leap years.

the only real number should be when the Earth was created, and not when Humans decided to keep count

or since the Big Bang, as Humans are not the center of everything

so about 20GY ( or 80GY )

you forgot the dinosaurs age, time didnt started with the birth of jesus, dalai lama, velociraptors, or even when the earth was created.

The most correct answer for the time in our universe is year 13.7 billion... but then again we have einstein theory of relativity, so the time we live in this planet is different of the time we live when flying on a plane.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      599
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!