[Solved] PHP to become ahead of time compiled language? [closed]

Question

When Python code is first invoked, it (usually) is parsed/interpreted once into byte code and saved in a .pyc file and then executed. The next time the code is invoked, the ahead-of-time interpreted byte code is found in the .pyc file and that is executed.

For PHP, since PHP 5.5, an opcode cache has been included. When PHP code is first invoked, it (usually) is parsed/interpreted once into byte code and saved in the opcode cache and then exectued. The next time the code is invoked, the ahead-of-time interpreted byte code is found in the opcode cache and that is executed.

Byte code is close enough in performance to native code. There is not much motiviation for compiling ahead of time to native for eitther Python or PHP. You would give up the fast edit-save-reload-browser development cycle for unneeded gains in performance.

Accepted Answer

When Python code is first invoked, it (usually) is parsed/interpreted once into byte code and saved in a .pyc file and then executed. The next time the code is invoked, the ahead-of-time interpreted byte code is found in the .pyc file and that is executed.

For PHP, since PHP 5.5, an opcode cache has been included. When PHP code is first invoked, it (usually) is parsed/interpreted once into byte code and saved in the opcode cache and then exectued. The next time the code is invoked, the ahead-of-time interpreted byte code is found in the opcode cache and that is executed.

Byte code is close enough in performance to native code. There is not much motiviation for compiling ahead of time to native for eitther Python or PHP. You would give up the fast edit-save-reload-browser development cycle for unneeded gains in performance.