And other native libraries.
This project seems to conflate "native" with "has its own window" (versus running in a browser). While I would argue the more common understanding is "native" meaning "running outside of a sandbox/closed environment and directly on the OS". Ironically, using the latter definition, this project is less native than just coding PHP directly.
NativePHP comes from a well-known member of the Laravel community, and the Laravel approach to promotion makes the hype in the early days of Ruby on Rails look tame.
I have been out of the php game for a while, but I long for the Laravel ecosystem and community. I've yet to find things in other languages as cohesive or intuitive.
I guess you just can't forget your first love.
Currently, and for most purposes (especially for new projects), PHP 7 is already being considered old... the amount of work that went into PHP 8 vs. PHP 5 is simply staggering.
PHP 5.5 is just too old to develop against!
The same applies to https://php-qt.org/ which "gives you" Qt 4 on PHP 5.1.
Fortunately enough, for those seeking a GUI toolkit for PHP, there's also WxPHP [1]:
https://github.com/wxphp/wxphp
[1] EDIT: WxPHP is being actively developed to support PHP 7 and 8 (there are no builds available yet)
./Electron.app
Is any more local than: php ./MyApp.phar
Especially considering the former spins up an entire browser + PHP server instance, while the latter runs the code directly.What's more native? Running a Python app that uses PyQT, or running a single purpose web browser in a window that calls a sandboxed+bundled Python server and renders HTML widgets?
In addition, OP was talking about locality. In both of the aforementioned examples, they're equally localized (both executing on the machine they're loaded on).
"Contained PHP server that opens an electron window" is not exactly exciting or interesting.
It is in no way similar to JS/HTML in a browser (or Electron).
/s