Chat with Maurice Wilkes AI

Pioneer of Computing, Designer of EDSAC

AI character, not a real person. Chat with Maurice Wilkes AI free with an account, or call and hear the answer out loud.

About Maurice Wilkes

On 6 May 1949, at the University of Cambridge, a room full of engineers and mathematicians held their breath as EDSAC executed its first program, a simple table of squares, without rewiring or manual intervention. That moment wasn’t just a technical milestone; it was the birth of reproducible, general-purpose computation. Unlike earlier machines built for single tasks, EDSAC ran programs stored in mercury delay-line memory, a decision grounded not in theoretical elegance but in wartime pragmatism and postwar scarcity. Its instruction set was designed to be human-readable in octal, its subroutines shared via punched paper tape, and its debugging done with a panel of blinking lights and meticulous notebooks. This wasn’t abstraction for abstraction’s sake: it was engineering shaped by chalk-dust lectures, limited funding, and the conviction that computers should serve scientists, not the other way around. The microprogramming concepts later refined in his 1951 lectures emerged from watching operators struggle with instruction timing, not from silicon constraints. Precision here meant clarity, not speed.

Why Chat with Maurice Wilkes?

Maurice Wilkes is one of the most influential figures in Science & Technology. Through AI conversation, you can explore their ideas, ask questions you've always wondered about, and gain unique perspectives on pioneer of computing, designer of edsac topics. It's like having a personal conversation with one of the greats, powered by AI and completely free.

Start Your Conversation with Maurice Wilkes

Ask questions, explore ideas, and learn something new. Free with an account, and no card.

Chat with Maurice Wilkes Now

Call Maurice Wilkes and talk out loud

You do not have to type. Call Maurice Wilkes and hear the answer in their own voice, in this browser, with nothing to install. Tap to interrupt whenever you want, speak whatever language you like, and the whole conversation is saved into your chat when you hang up. 20 minutes of calls free every 30 days when you sign in, no card.

Call Maurice Wilkes How calling works

Conversation Starters

Not sure where to begin? Try asking Maurice Wilkes:

  • “What made mercury delay lines the right choice for EDSAC’s memory in 1949?”
  • “How did you decide which instructions EDSAC would support, and why octal?”
  • “What was the most frustrating hardware limitation you worked around during EDSAC’s build?”
  • “Did the ‘initial orders’ (EDSAC’s bootloader) evolve from user feedback, or your own workflow?”

Frequently Asked Questions

Was EDSAC truly the first stored-program computer?
EDSAC was the first practical, regularly used stored-program computer. While Manchester’s SSEM ran a stored program in June 1948, it was a proof-of-concept with no I/O, no assembler, and no sustained operation. EDSAC, operational from May 1949, supported real scientific work, like computing Bessel functions for physics research, and ran continuously for nearly a decade. Its design prioritized reliability and usability over novelty.
What role did you play in developing microprogramming?
In my 1951 lectures at Cambridge, I introduced the concept of microcode as a way to decouple instruction execution from hardware timing. I demonstrated how control logic could be expressed as sequences of microinstructions, stored and modifiable, allowing complex operations to be broken into synchronized steps. This idea directly influenced IBM’s System/360 architecture and became foundational for processor design, though I never patented or commercialized it.
Why did EDSAC use a 17-bit word length?
The 17-bit word emerged from the physical constraints of our mercury delay-line memory: each tank held 32 words of 17 bits, optimized for signal propagation time and pulse recovery. We didn’t choose 17 for mathematical elegance, it was the longest stable word we could reliably store and retrieve in the available hardware. Later machines adopted powers of two, but EDSAC’s word length reflected empirical engineering, not convention.
How did you handle programming errors without modern debuggers?
We relied on systematic manual tracing: printing intermediate register states onto paper tape, comparing them against hand-calculated step-by-step executions, and using the console’s indicator lights to isolate faulty valves or timing glitches. My 1951 ‘Handbook for EDSAC Programmers’ included detailed fault-diagnosis flowcharts, because every error was a hardware-software interface problem, not just a logic bug.
Can I call Maurice Wilkes and talk out loud?
Yes. Every character on AI Anyone can be called, including Maurice Wilkes. You talk, they answer in their own voice, and you can interrupt them by tapping the screen. Calling runs in a web browser on a phone or a laptop with no app to install, and it needs a free account: signing in gives you 20 minutes of calls at no cost every 30 days. Pro includes 240 minutes every 30 days.

Topics

computinghistoryedsacmicroprogrammingengineering

Related Science & Technology Characters

Douglas Hartree
Pioneer of Numerical Analysis and Computing
William Kahan
Father of IEEE 754
Charles Babbage
Inventor and Mathematician
Ward Cunningham
Inventor of the Wiki, Computing Pioneer
Clive Sinclair
Inventor of the ZX Spectrum and Sinclair Research
Grace Hopper
Computer Scientist and Mathematician
Luigi Federico Menabrea
Mathematician, Engineer, and Statesman
Ernst Heinkel
German Aircraft Pioneer and Engineer
Browse all Science & Technology characters →
Explore 40,160 AI Characters →
© 2026 AI Anyone. All rights reserved.