Parent's point was that while those phrases sound like word jumble to some, they actually have very specific and well-understood meanings.
Imagine a non-techie person listen to two software engineers talking. Closures, event bubbling, monads, abstract classes - they'd say the same thing.
Can someone without CS / programming knowledge really judge a good abstraction versus a bad one? Similarly, it's arrogant of us to assume we can do the same in the humanities, because it means we assume the humanities are easy / trivial and so on, which they are not.
It's like the "my kid could paint that" cliche of Modernist painting - maybe your kid could, but, you saying that just indicates that you aren't educated about what the artist is doing, why they choose to do it, and the previous works of art the artist is responding to or in dialogue with.
Kind of like, "why can't everything be HTML/CSS, with maybe a little JQuery?" Sure, you have a point, but there are clearly more sophisticated use-cases where that approach is not the most effective, and, your saying that kinda indicates you may not have encountered or had to deal with those use-cases.
Truth be told I think computer science, at least the parts of it where you get to create abstractions which then define the bounds of what is possible within that programming paradigm (see - word jumble!) is closer to the "soft" humanities than many are aware of or would care to see.
Tech folks tend to love/desire "certainty" in one form another, and, the easiest way to achieve that is to rule out everything which is "uncertain", and, constrain your domain until "certainty" can be achieved. Which can be a great approach for certain technical problems, but also IMHO results in ignorant behavior towards anything which threatens said certainty.