what does AD means ?


Recommended Posts

Anybody understand calender thingies better ?

What does AD means ?

I guess ..AD = After Death of Christ.

The reason I am asking , I found a text written as..In the Buddhist year of 1974 ( 1421 AD )....

Does 1974 = 1421 AD ...really ? whats the math here ?

A.D. means Anno Domini.

"Refers to the traditionally reckoned year of the conception or birth of Jesus, with AD denoting years after the start of this epoch, and BC denoting years before the start of this epoch. There is no year zero in this scheme, so the year AD 1 immediately follows the year 1 BC." - Wikipedia

So, the Buddhist year of 1974 would be 1421 C.E. (Common Era, or A.D.: Anno Domini), and the 'math' that you are looking for is:

2009-1421 = 588 years.

Therefore, whatever you are reading occurred 588 years before 2009, our current year.

As pointed out by The_Decryptor, not everybody in the world uses the calendar that we are familiar with.

Its still pretty confusing thing.

Ok, let me say what i get .

We have various Calender Systems....Most of the countries in the world uses Gregorian calendar ....but still there are some countries where Buddhist_calendar is used ( Example Thailand).

Now , when we say 1421 AD ..I believe this does not come under the above two Calender ...right ? So, we have to convert it to our familiar Calender ....right ?

If that is so, whats 1421 AD in Gregorian calendar ?

A.D. means Anno Domini.

"Refers to the traditionally reckoned year of the conception or birth of Jesus, with AD denoting years after the start of this epoch, and BC denoting years before the start of this epoch. There is no year zero in this scheme, so the year AD 1 immediately follows the year 1 BC." - Wikipedia

So, the Buddhist year of 1974 would be 1421 C.E. (Common Era, or A.D., Anno Domini), and the 'math' that you are looking for is:

2009-1421 = 588 years.

Therefore, whatever you are reading occurred 588 years before 2009, our current year.

As pointed out by The_Decryptor, not everybody in the world uses the calendar that we are familiar with.

Thanks for the information ... that was a hell lot of nice stuffs !

but still, I am not clear with this AD & BC stuff.

do you means AD 's are counted after the birth of Christ ? So, if I say 5 AD ...does that mean the concerned year we are talking is 5 year after the birth of Christ ? Am i correct now ?

Its still pretty confusing thing.

Ok, let me say what i get .

We have various Calender Systems....Most of the countries in the world uses Gregorian calendar ....but still there are some countries where Buddhist_calendar is used ( Example Thailand).

Now , when we say 1421 AD ..I believe this does not come under the above two Calender ...right ? So, we have to convert it to our familiar Calender ....right ?

If that is so, whats 1421 AD in Gregorian calendar ?

No, 1241 A.D. already denotes that it refers to the year 1241 in the Gregorian calendar.

Thanks for the information ... that was a hell lot of nice stuffs !

but still, I am not clear with this AD & BC stuff.

do you means AD 's are counted after the birth of Christ ? So, if I say 5 AD ...does that mean the concerned year we are talking is 5 year after the birth of Christ ? Am i correct now ?

Yes, that is correct. It is the way it works.

Thanks for the information ... that was a hell lot of nice stuffs !

but still, I am not clear with this AD & BC stuff.

do you means AD 's are counted after the birth of Christ ? So, if I say 5 AD ...does that mean the concerned year we are talking is 5 year after the birth of Christ ? Am i correct now ?

Well, it just denotes 5 years from an epoch that was decided to be the birth of "christ"

An Epoch is just a common point in time, if we define January 1st, 2000 to be an epoch then we could say it's 9 years "AY2K" (After Year 2000)

Ok ...Thats good info .

>>>1241 A.D. already denotes that it refers to the year 1241 in the Gregorian calendar.

So, you mean AD/BC's are refers to the year in the Gregorian calendar.....ok....fine...cool.

If that is also true , then we can write current year 2009 as 2009 A.D ...right ? Can we write this ? any problem ?

Ok ...Thats good info .

>>>1241 A.D. already denotes that it refers to the year 1241 in the Gregorian calendar.

So, you mean AD/BC's are refers to the year in the Gregorian calendar.....ok....fine...cool.

If that is also true , then we can write current year 2009 as 2009 A.D ...right ? Can we write this ? any problem ?

Yes, you can write 2009 A.D., instead of just 2009. :laugh:

A.D. and B.C. are just designations.

Yes, you can write 2009 A.D., instead of just 2009. :laugh:

A.D. and B.C. are just designations.

ahhh....You made me so happy :)

just one more doubt here.

Suppose, If I say the story is of the time of 10 BC ...that means we are talking about a story of approximately (2009 + 10 )= 2019 years ago . // I did addition because BC = before the birth of Christ ...hence more older

Am I correct in this math ?

Yes, some of the confusion in this thread is coming from the fact the some do not like to use Christian references. Hence we're seeing terms like Common Era (CE) instead of Anno Domini (AD) and Before Common Era (BCE) instead of Before Christ (BC).

In a multicultural modern world it is a bit insensitive (not to mention stylistically dated) to use BC/AD. You'll find that most encyclopedias and other scholarly work has switched to using BCE/CE.

ahhh....You made me so happy :)

just one more doubt here.

Suppose, If I say the story is of the time of 10 BC ...that means we are talking about a story of approximately (2009 + 10 )= 2019 years ago . // I did addition because BC = before the birth of Christ ...hence more older

Am I correct in this math ?

Can't see any flaw with it.

You don't really need to use the suffix unless you're referring to a date B.C (or BCE, whatever), nobody's going to think World War 2 started in 1939 BC (for example)

Yes, some of the confusion in this thread is coming from the fact the some do not like to use Christian references. Hence we're seeing terms like Common Era (CE) instead of Anno Domini (AD) and Before Common Era (BCE) instead of Before Christ (BC).

In a multicultural modern world it is a bit insensitive (not to mention stylistically dated) to use BC/AD. You'll find that most encyclopedias and other scholarly work has switched to using BCE/CE.

I don't see a confusion in the thread deriving from the reason that you have stated.

ahhh....You made me so happy :)

just one more doubt here.

Suppose, If I say the story is of the time of 10 BC ...that means we are talking about a story of approximately (2009 + 10 )= 2019 years ago . // I did addition because BC = before the birth of Christ ...hence more older

Am I correct in this math ?

You are correct.

So, what year did Jesus die?

He supposedly died when he was 33.

If you assume that he was born on year 1 then that would mean the year 34. However, most experts dispute the date of Jesus' birth. It would seem that Jesus was most likely born in 4BC or slightly before. Anything from the year 27 to the year 39 is possible.

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

    • No registered users viewing this page.
  • Posts

    • 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.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!