To the contrary, TeX (not LaTeX) has one of the best error-handling and error-recovery interfaces of any commandline program — if you use TeX as Knuth intended, that is, if you use plain TeX at the commandline and if you have read the entertaining chapters in The TeXbook on dealing with errors. Just try using plain TeX (not LaTeX) for a few months and you'll find that the behaviour when errors happen is one of its delights, the opposite experience from when you use LaTeX. (Of course, you may miss many conveniences from LaTeX, but the error experience is itself almost worth the change.)

Knuth has done a great job that should be the model for all other software writers: every error is described in two ways, one somewhat formal and one somewhat informal, and every error is shown with enough context (and this is configurable too) for you to quickly see what the issue is, and you can even fix errors without having to abort the compilation. He has a great talk where he describes how the English language is optimized for dialogue (things like "I" and "you") and TeX messages are designed in that way.

Unfortunately, LaTeX consists of several layers of complicated macros (all in the name of making things convenient for, and hiding things from, the user) and as they (correctly) decide that all these layers won't make sense to the user, they actually turn off all the context that goes with the error, leading to error messages that are incomprehensible even to experts. But I don't think it's right to blame the fact that LaTeX didn't bother to implement good error-recovery on TeX.