3 ms·
Technologically it's not a big deal for developers who want to run PHP on Windows because WSL can do that. It might affect people who have, say, a .NET app runn
by onion2k 6y ago
Technologically it's not a big deal for developers who want to run PHP on Windows because WSL can do that. It might affect people who have, say, a .NET app running on Windows in Azure who wanted to put a Wordpress marketing site on the same server. As of PHP8 they'll have to either use an 'unofficial' PHP build for Windows or move the PHP site to a second server.
Politically though, it might be a big deal. Microsoft don't think supporting a native Windows build of PHP is worthwhile. That could say something about the server-side scripting language landscape changing. On the other hand, it might just say that it costs a few hundred thousand dollars of engineering time every year and they believe that could be allocated better. There's no way to know from a single post.
- int_19h 6y agoWith WSL getting popular, between that and native build, there's two different versions of PHP to support on Windows in practice. And, given that WSL maps closer to production environments for most use cases, it's clear that it's the more important one.
- tpetry 6y agoI guess the just have to make to many modifications to run 8.0 on Windows. Maybe the JIT does nor work properly/easily on windows? Nevertheless nowadays there is WSL and Docker so you don‘t really need a windows native executable.
- innocenat 6y agoThere already PHP8 build on Windows: https://windows.php.net/qa/ https://windows.php.net/qa/