Defining Redux Middleware

Blog

So, I'm reading an article about redux middleware, becoming increasing annoyed by the author who writes 6 paragraphs about why he wrote this article I'm reading, when I come to the section where, hey, he's actually defining what middleware is, and he states:

The most concise definition I can give to describe middleware is this:

Middleware is created by composing functionality that wraps cross-cutting concerns which are not part of your main execution task.

Okay, when you are defining something, ACTUALLY DEFINE IT. You don't define something by using any verb that is not a linking verb. Here, definitions go like this:

Object is {what the object is}

It is not, Object is created by or Object goes something like this. Don't use examples as a definition, PROVIDE THE DEFINITION.

So, no, while middleware might be created by composing functionality, that is not the definition. Here, the definition: Middleware is software that bridges two parts of an application or a system. That's it. "Composing functionality" and "cross-cutting concerns" is crap-speak for "I don't really know what this is doing, so I'm going to use big words."

Now, in this case, redux middleware is the software that connects a react state with the state storage system (which is what redux nominally is).

Done. Simple. Why was that so hard?