> Are these middleware components that someone else is supposed to package together into something useful like a platform? The other bits lead me to think it's a platform of sorts in itself. So, why the talk of middleware?

It's intended to be usable as a single installation with the option to install individual parts. The textbook case is Build -- you can get things done with or without it.

> Are these reusable components supposed to be packaged in a higher level system? It sounds like that but other parts of the page suggest it's a platform to use now.

I think a bit of both. The joke I've made is that if Kubernetes is IaaS++, Knative is PaaS--. It's usable as-is, it aims to provide a common set of primitives for shared concerns, but it can also serve as a base for higher-level systems. The Project riff team, for example, have pushed some of their efforts down into Knative.

> In my experience they like shorter form ones (there are numerous tools making that possible).

Mine too. My personal view is that Build (and before long Pipelines) will be the main entryway to Knative.