In automata theory, the fundamental questions about computational problems should focus on time and space complexity rather than whether a particular automaton architecture can recognize a language; this insight emerged from Ullman and Hopcroft's work on stack automata, which demonstrated that the organization of a program matters less than its resource efficiency.
Deep Dive
Prerequisite Knowledge
- No data available.
Where to go next
- No data available.
Deep Dive
“A Lesson in What Not To Do” – Ullman Explains His Work on Automata Theory with HopcroftAdded:
there was a a sense, okay, finite automata really interesting. You use them in in lexical analyzers and they they model uh simple protocols of of all sorts and and and context-free grammars, languages are obviously important in in in parsing.
Uh so, let's look at all other let's try to invent other kinds of automata.
Uh and and see what they can do.
And that turned out to actually be a a misguided approach. What we were really looking at was structure of or- organization of a of a program. So, for example, we looked at stack automata, which was an an idea that um Seymour Ginsburg had had had where uh uh you know, the no- normal parsers were was a pushdown automaton in the sense that you have a stack. You know, that that you just operate move you know, inserting and deleting at the top of of the stack.
Hopcroft and I we we proved some very very complicated, or at least for the time complicated, facts about what kind of languages you could you could recognize uh if a in using that ar- architecture, but thing is, you don't pay for organization.
You pay for time, you pay for space.
Okay.
And that's why all of the all of the you know, questions about can this kind of automaton recognize this language or do this uh you know, implement this this solve this problem turn out to be irrelevant.
The only questions that are really interesting are how much time and how much space does it take to solve a problem.
Okay.
Um That's That's one of the great lessons, I think, that I that I I I learned about what not to do.
What did we know at the time? All right.
We uh um uh You know, it it it seemed like interesting questions, so we we asked them and tried to answer them.
Related Videos
Agentforce NOW AMA: Build with React and Salesforce Multi-Framework
SalesforceDevs
490 views•2026-05-28
How agent o11y differs from traditional o11y — Phil Hetzel, Braintrust
aiDotEngineer
450 views•2026-05-28
WEB TECHNOLOGIES UNIT-2 | Degree 4th sem BCOM Computers web technologies unit-2 full explanation💯✅
LearnwithSahera
1K views•2026-05-29
More tests are always better? How to use AI to identify tests that bring little value
Alliance4Qualification
335 views•2026-05-29
Search Algorithms Explained in 60 Seconds! 🤖💨
samarthtuliofficial
218 views•2026-06-01
People of Game of Thrones using JavaScript DOM
AltCampus
296 views•2026-05-30
Introduction to Problem Solving Part - 1 | Lecture 1 | Intermediate DSA
ascensionix
107 views•2026-05-29
So What's Odin Lang Even Good For
TechOverTea
131 views•2026-06-01











