...but last time i checked PHP itself was a templating system. What changed?
All of these features and more have to be implemented as a third party framework for PHP to be effective as a templating system, which is why such systems exist.
Merely echoing HTML strings and wrapping variables in htmlspecialchars() does not a "templating system" make. If it did, then every programming language would also be a templating system as long as it could output a string of characters to the necessary port.
It has been a very very long time since i used PHP for anything serious (or did any web programming at all) but to me that sounds like templates. Perhaps you are referring to something else with the word "template"?
Because PHP, natively, doesn't provide the features that a modern template system needs to be safe, scalable or productive. PHP doesn't recognize HTML or XML as a type, or a "template" as a thing, automatically escape user supplied data (correctly, based on context) or correctly deduce content-type headers or route requests or any number of things one expects of a modern framework or templates. As a PHP application grows in complexity, you will, inevitably, find yourself reinventing frameworks. So might as well just use one that's already been proven in the wild and optimized.
All PHP has is string concatenation. It's "templating system" is blind string concatenation - that's it.
> Streaming server rendering allows you to send HTML in chunks that the browser can progressively render as it's received.
Hasn't PHP done this by default since, like, forever?