we have attempted to use it for that, but it was really hard and we ended up rewriting from scratch.
The activity graph on GitHub says it is mostly dead. There is some activity, but at best it is in maintenance mode. It used to be sponsored, but not anymore IIRC
A major difference will be that PeachPie produces a compiled deploy artefact, while mainstream PHP is interpreted (albeit with heavy opcode caching and a JIT in production)
Comments
Migrating a legacy PHP code-base to .net maybe
we have attempted to use it for that, but it was really hard and we ended up rewriting from scratch.
The activity graph on GitHub says it is mostly dead. There is some activity, but at best it is in maintenance mode. It used to be sponsored, but not anymore IIRC
https://github.com/peachpiecompiler/peachpie/graphs/contribu...
It looks like this compiles PHP code to a .net binary but it doesn't support all of PHP so it's kinda useless for most projects.
Benefits of this are dubious at best. The php interpreter is already a low level C project so why replace that with .net? Makes no sense.
A major difference will be that PeachPie produces a compiled deploy artefact, while mainstream PHP is interpreted (albeit with heavy opcode caching and a JIT in production)
You are comparing apples with pies here. PHP is a interpreted language, while .NET is a compiled target.
However, this peachpie project seems to be far from stated goal and more of a research project currently.