1. 12

  2. 2

    Interesting ideas but the title is a bit sensational; PHP was always meant to die (that is, the process after serving a page to one person) but now that it’s become modernized and with the help of new technologies it doesn’t have to.

    1. 1

      Mkay, so, five or ten years ago, it was considered keeping a PHP interpreter hanging around for many many requests was a fairly bad idea because none of the code in the ecosystem had really been extensively tested in that mode of operation, so all kinds of memory leak bugs were left around.

      (IMO they were not really bugs, just absence of support for the “long lived process” use case.)

      I take it that that class of problem is largely fixed now in the modern PHP ecosystem?

      1. 1

        Yes, with the release of PHP 7 a lot of the internals were reworked.