Academic research and education is normally focused on silo'd content and not holistic system design. To use your example, a parser that gracefully handles bad

Academic research and education is normally focused on silo'd content and not holistic system design. To use your example, a parser that gracefully handles bad input is a completely different region of study than simple parsing/grammars. It's outside the context. That does not mean that academia does not cover the topic, you just probably wouldn't get to it in an undergraduate course on (frankly trivial) compilers and parsers. If you read into research on things like semantic fuzzing, the slow death of batch compilers, and the various error propagation mechanisms out there from PL researchers you'd see those topics bring up lively academic discussions. Academia lags in many ways behind practical designs because they aren't governed by deadlines and market realities, but they lead in many others precisely because ideas aren't constrained and they can focus on things that don't have immediate value to markets. It's not wise to discount an entire domain of expertise and culture of development just because it exists in a different context than professional engineering, particularly when we owe our entire industry to the efforts of academics in the first place.