Getting Started With Ancient Times A History Of The Early World

I picked this up about a year ago after someone recommended it as a supplement to my own reading on early civilizations. The premise is straightforward — it walks through human history from roughly 10,000 BCE through the fall of major ancient empires, covering Mesopotamia, Egypt, the Indus Valley, early China, and the Mediterranean world. The production quality is decent but not polished. You can find the download at the official site, though the interface is clunky and the file sizes are large. It is a multimedia educational resource, not a documentary series and not a textbook replacement. Think of it as a structured timeline with companion readings, maps, and occasional video lectures attached to key periods. The content itself is solid — the author clearly did their homework on primary sources and recent archaeological findings. The main weakness is that it treats these topics as somewhat disconnected rather than showing how they influenced each other. You will get a chapter on Sumer and then jump to the Nile without much explanation of trade routes or migration patterns between the two. The download comes in chunks. Each civilization module is separate, which is convenient if you only care about one region, but it means you need to install them in a somewhat logical order or you will find yourself jumping around without context. I would start with Mesopotamia, then move to Egypt, then the broader Bronze Age collapse material before branching out into other areas.

Installation and Setup — The Parts They Do Not Tell You

Here is the first problem I ran into: the install requires about 12 gigabytes of free space and the initial setup takes roughly twenty minutes on a decent machine. I assumed it was going to be a quick download and launch situation. It is not. The installer checks for Java runtime and a few other dependencies that are not clearly listed on the download page. I wasted about an hour tracking down the right Java version before anything would open. Make sure you have Java 11 or higher installed before you start. Another thing nobody mentions is that the in-app reference library, which contains all the source texts and maps, is not included in the base install. You have to download it separately after setup completes. It is another 4 GB file that downloads through the application itself, not through your browser. If you have a slow or metered connection, this is where you will hit a wall. Plan for that. Once everything is installed, the main interface loads slowly on older hardware. I got acceptable performance on a machine with 16 GB of RAM and an SSD, but on a laptop with integrated graphics, the timeline navigation stutters noticeably. This is not a dealbreaker but it is annoying if you are trying to quickly jump between time periods for reference.

How to Actually Use It Effectively

The biggest mistake people make is treating it like something you watch passively. It works better if you treat it like a reference tool you go into with a specific question. Want to understand why the Bronze Age collapse happened? Pull up that module and read the companion essays first, then watch the lecture videos. The videos are supplementary, not the main event. The essays and primary source excerpts are where the actual learning happens. The map layer is the strongest feature. The interactive maps show territorial changes over time with sliders, so you can drag through centuries and watch how empires expanded or contracted. I spent most of my time using this feature rather than the linear timeline. It gives you a much better spatial understanding of why certain civilizations rose where they did and why others faded. One thing the resource handles well is the distinction between myth and documented history. The Egypt module, for instance, clearly separates the legendary early pharaohs from the archaeologically verified ones. That level of honesty about the source material is rare in resources aimed at general audiences. Most people skip past that nuance and just want a clean narrative. The author does not do that, which makes it more trustworthy even when the presentation is dry.

Get the Full Details

Artesian Well : Pros and Cons of Artesian Wells Explained With ...
Artesian Well : Pros and Cons of Artesian Wells Explained With ...

What It Gets Wrong

For all its strengths, there are gaps. The Indus Valley section is underdeveloped compared to Mesopotamia and Egypt, which is partly a reflection of the actual scholarly imbalance in the field but still frustrating for anyone interested in South Asian early history. The section on early Chinese dynasties is similarly thin, relying heavily on traditional chronologies that newer research has complicated. If you already have some background knowledge, you will notice these omissions. If you do not, you might walk away with an incomplete picture. The dating system used throughout is conventional dates rather than calibrated radiocarbon ranges. This means some of the timelines presented could be off by a few decades depending on where you read the scholarship. It is a minor issue for casual learning but it matters if you are using this for academic work or serious study. There is also no built-in note-taking or bookmarking system. I ended up keeping a separate document where I recorded timestamps and chapter references for anything I wanted to come back to. This is a basic feature that should have been included, and its absence makes long-term use significantly less convenient.

Bottom Line

Ancient Times A History Of The Early World is worth having if you are genuinely interested in early history and want a structured resource that does not dumb things down too much. It is not the best standalone introduction — for that you would be better served by a textbook or a university lecture series. But as a supplementary reference with good maps and primary source access, it fills a real niche. Just budget extra time for installation, make sure your system meets the requirements, and go in with the expectation that you will need to do some of your own connecting between modules.