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

    • Qwen 3.6 is better value per dollar, and you can run it locally for free.
    • I don't believe them that anyone using threads, at least meaningfully. It's the same thing for Facebook, people just don't engage with Meta platforms like they are thinking. This isn't 2006.
    • Not taking AI slop on the go with me, hard pass for me.
    • Same Internet Archive seemed to grab the new version https://web.archive.org/web/20...d/Setup_MakeMKV_v1.18.4.exe Here's the link to an additional file it periodically downloads https://web.archive.org/web/20260213092148/https://www.makemkv.com/sdf.bin I think update's keys, etc. To manually trigger this update, put the sdf.bin file in the root of where the program is installed. When you launch the program it will pick up the file and import it. Typically put it here: C:\Program Files (x86)\MakeMKV\sdf.bin
    • Windows 11 KB5094126, KB5093998 bugging out Office apps but it may not be Microsoft's fault by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. Although the tech giant did not acknowledge any major problems, some users online reported various issues ranging from OneDrive and Dropbox access problems, BitLocker recovery lockouts, to blue screens and BSODs. You can read about them in this dedicated piece. While there is still no confirmation about those problems from Microsoft the company has admitted to another bug which we did not report on. The tech giant has confirmed it has received reports of an issue in which certain third-party applications may be unable to launch Microsoft Office apps or open Office documents after installing the Patch Tuesday. This affects both Windows 11 as well as Windows 10. The company says the problem impacts a subset of applications that rely on OLE (Object Linking and Embedding) automation to communicate with Microsoft Office programs. According to Microsoft, affected scenarios involve third-party software attempting to open Office applications or documents from within their own interface. In such cases, the Office program may fail to launch altogether, or the requested document may not open. Oddly there may not be any error message, which probably makes the issue difficult to diagnose. The bug affects several Office products, including Word, Excel, PowerPoint, Access, and other apps in the Microsoft Office suite when they are launched through the affected software. These include tax and accounting software such as CCH Engagement and Workpaper Manager, dental practice management solutions like Dentrix and Softdent, as well as the popular research and reference management tool Zotero. Microsoft adds that other applications using similar Office integration methods could also experience the same problematic behavior. To understand the issue it is important to look at OLE, the Microsoft technology involved. OLE allows different applications to work together and share data, while its Automation feature lets one program control another. Thus this enables third-party software to launch Microsoft Office apps, open documents, and perform tasks automatically without requiring users to switch between programs. Because many accounting, healthcare, research, and business applications rely on OLE automation to interact with Word, Excel, PowerPoint, and other Office apps, any disruption can break those workflows. As a result, affected software may be unable to open Office documents or launch Office applications even though the programs themselves continue to work normally. At the moment the company has not provided a permanent fix though it has confirmed that engineers are actively working on a resolution, which will be delivered through a future Windows update. As such additional details will be shared once more information becomes available. In the meantime, Microsoft recommends a simple workaround for affected users whic is to open the Office application or document directly rather than launching it through the third-party program. For enterprise customers and organizations managing larger deployments, Microsoft says an additional mitigation is available. Admins experiencing the problem on their managed devices are advised to contact Microsoft Support for business to obtain and apply the workaround.
  • Recent Achievements

    • Reacting Well
      Dys Topia earned a badge
      Reacting Well
    • Conversation Starter
      NovaEdgeX earned a badge
      Conversation Starter
    • One Year In
      Console General earned a badge
      One Year In
    • Week One Done
      Twozo Technologies earned a badge
      Week One Done
    • One Month Later
      Twozo Technologies earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      517
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      106
    4. 4
      Steven P.
      88
    5. 5
      ATLien_0
      68
  • Tell a friend

    Love Neowin? Tell a friend!