> No! PSR creates so-called standards for interoperability between frameworks,

Yes, but this is not the perception in the PHP dev community writ-large and perception is reality.

> keep up the good work (and the `StreamInterface`)

As I've said before: `StreamInterface` *is* a nice abstraction. However, standardizing it in an "HTTP Message Protocol" with a **MUST** modifier is a mistake. That's a serious overreach as language-specific internal data structure access and memory-management is totally unrelated to HTTP or HTTP messages.

Every language `*SGI` standard of consequence defines requests and responses in terms of native datastructures. See Perl's PSGI, Python's WSGI ... While I'm not advocating storing everything in arrays willy-nilly I'm hopefully pointing out *why* it's necessary to avoid *restricting* functionality and putting a ceiling on performance in standards. Otherwise you end up with what PHP web SAPI has now: a slew of frameworks that rate at the very bottom in terms of performance in every available benchmark.

If PHP frameworks are to stay relevant it won't be because HHVM rescues them from themselves: it will be because they stop enforcing behaviors that limit performance. Interfaces like `Message/Request/Response` make sense because they don't have native compiled equivalents in the language. PHP already has stream abstractions and *requiring* `StreamInterface` as part of a "standard" is a mistake.

I'm fully in favor of a **SHOULD** modifier for something like `StreamInterface`, but its requirement is a mistake.