PeachPie VS P

PeachPie may be worth a look. It’s a php to .net compiler.

https://www.peachpie.io/

It’s one of the most popular languages that is used to web apps at enterprise scale. You want useful? https://www.peachpie.io

Honestly it sounds like you’re in for a rough time. But here’s a real answer: https://www.peachpie.io

If you're planning to move more than 1 project toward C#, look into PeachPie, depending on the complexity of the API your project should run out of the box with no issues. This should let you rewrite the hot paths in C# while leaving rest of the system written in PHP(while still running in the .NET eco system).

We had to format the code for this article. You can find this method by following the link.

For IronPython's case there are interested parties, but it's not as large so you don't hear much about them. Same goes for the more niche stuff like peachpie where it's pretty active (dev-wise) but there's not much talk about it as there isn't as much community interest on following the project.

It's been a while since we posted articles on the C# projects check using PVS-Studio... And we still have to make the 2021 Top list of bugs (by the way, 2020 Top 10 bugs, you can find here)! Well, we need to mend our ways. I am excited to show you a review of the PeachPie check results.

I worked on a state machine framework in another language, and have definitely have found less terse to be pretty good. Typing a few extra characters isn't that bad, especially if it makes some awful bit of evented code easier for someone to understand.

Of the things available open source, I think P-lang is pretty cool: https://github.com/p-org/P/blob/master/Tutorial/1_ClientServ...

Your proposed syntax reminded me of https://p-org.github.io/P/

I’ve gotten a lot of good about TLA+ and the more recent the P language has been really promising lately. It’s got a good pedigree and is being increasingly used as AWS as well.

I tried to use TLA+ but what annoys me the most is the disconnection between the actual implementation and its code. I think the P language has a much better future just because it can generate code that works: https://github.com/p-org/P

It is tough.

My approach when learning new protocols like Raft or Paxos is to implement them in Pluscal (TLA+'s higher-level language) or P (https://github.com/p-org/P). I've found that helps separate the protocol-level concerns from the implementation-level concerns (sockets? wire format?) in a way that reduces the difficulty of learning the protocol.