3 ms·

What does this actually mean? The PHP release engineer who replied didn’t make it sound like it was a major deal (of course, if it is a major deal, this may jus

What does this actually mean? The PHP release engineer who replied didn’t make it sound like it was a major deal (of course, if it is a major deal, this may just have been an initial ACK statement).

tomhoward 6y ago
As I understand it, it's not a major deal now that WSL (Windows Subsystem for Linux) means you can run Linux software natively within the Windows environment. So, it's no longer necessary for PHP (or anything else Linux-y) to be natively supported on the Windows OS; anyone can just boot up WSL and run it there, where it will work better anyway.
- deleted 6y ago
  [deleted]
innocenat 6y ago
I guess they also have know-how on how to do the Windows build now. I remember before the windows.php.net day --- setting up PHP on Windows is much more of a mess that most people just use some kind of bundle (XAMPP, WAMP, etc)
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 ago
  With 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 ago
  I 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 ago
    There already PHP8 build on Windows: https://windows.php.net/qa/ https://windows.php.net/qa/
yyyk 6y ago
For now, probably not much, not even for PHP on Windows. I guess someone else will compile it. It would be a bigger deal for the few who run PHP on Windows, if WinCache or the SQL Server driver were dropped. * Used to run PHP on Windows, because $WORK had a tiny deployment that didn't need an extra server. In retrospect, getting a small cloud vm would have worked better, but letsencrypt wasn't around back then.

tomhoward 6y ago

As I understand it, it's not a major deal now that WSL (Windows Subsystem for Linux) means you can run Linux software natively within the Windows environment. So, it's no longer necessary for PHP (or anything else Linux-y) to be natively supported on the Windows OS; anyone can just boot up WSL and run it there, where it will work better anyway.

deleted 6y ago
[deleted]

innocenat 6y ago

I guess they also have know-how on how to do the Windows build now. I remember before the windows.php.net day --- setting up PHP on Windows is much more of a mess that most people just use some kind of bundle (XAMPP, WAMP, etc)

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 ago
With 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 ago
I 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 ago
  There already PHP8 build on Windows: https://windows.php.net/qa/ https://windows.php.net/qa/

yyyk 6y ago

For now, probably not much, not even for PHP on Windows. I guess someone else will compile it. It would be a bigger deal for the few who run PHP on Windows, if WinCache or the SQL Server driver were dropped. * Used to run PHP on Windows, because $WORK had a tiny deployment that didn't need an extra server. In retrospect, getting a small cloud vm would have worked better, but letsencrypt wasn't around back then.