I wonder if the problem is that names like "action","dispatcher","view" are abstractions that no longer (if ever) have a meaningful precise definition that can

I wonder if the problem is that names like "action","dispatcher","view" are abstractions that no longer (if ever) have a meaningful precise definition that can be understood independent of context in an application/framework. I'll refrain pointing at other examples from elsewhere. These terms seem like nice jargon to shorten discussions among people who already understand everything and just want to communicate quickly, but I don't think they help those outside who want to learn. I have no idea what the solution is since jargon probably can't be avoided, but perhaps my request would be that folks understand that the semantic meaning of these terms are not transportable across different domains; they are not self-evident and should not be expected that learners will infer good enough meaning from the term alone.