4 ms·

I didn't even know that Microsoft were the ones creating the official PHP builds, and now that I do, I have no idea why they were in the first place. Especially

I didn't even know that Microsoft were the ones creating the official PHP builds, and now that I do, I have no idea why they were in the first place. Especially not when PHP is software that's owned by a company that has had the resources to pay for normal CI/CD pretty much since PHP became big enough for Zend to hire staff.

johannes1234321 6y ago
The Microsoft guys did more than providing a CI. They cleaned up in regards to windows, whatever devs using Linux only did. Also they spent some time tuning the stack and continuous updates to the stack. Zend had nice marketing, but had been only one contributor under many. Far from owning PHP.
sedatk 6y ago
PHP was part of the IIS packaging and was marketed as a seamless integration option. That's probably why they worked on builds themselves.
- wutwutwutwut 6y ago
  > seamless integration option My experience with PHP on Windows has been continously terrible. Was there some trick I missed? I have never seen any options in a vanilla IIS to enable PHP.
  - stallmanite 6y ago
    I’ve been out of the PHP game for a decade or so but Windows, Apache, and PHP always worked no problem. Maybe Windows, IIS, and PHP is a more fickle stack?
    - DoctorOW 6y ago
      I have a tough time believing Microsoft wasn't intending their special builds of Windows PHP for IIS.