eslint-plugin-big-number-rules VS kphp

And they did bite me, so I wrote this eslint plugin to help out a FinTech app that was experiencing a number of such bugs.

Either avoid floating-point, perhaps using BigInt, or use a library like BigNumber.js. (Incidentally, I wrote an eslint plugin to enforce its use.)

I wrote an eslint plugin for it.

For example, say you want to avoid using native arithmetic in your finance calculations to avoid the infamous binary-floating-point problems. There's no way to get standard.js to warn you about that. But (warning: self promotion) an eslint plugin can be written to do that for you. :)

It has a lot of limitations but KPHP is a PHP compiler that could fit your needs.

There are also https://github.com/VKCOM/kphp, but it lag quite a bit behind php

JIT is still so full of bugs for anything mildly complex, most static analysers don’t run on it without some weird behaviour and crashes (segfaults, core dumps, etc) that are hard for the average PHP dev to debug. It was a nice idea to help expand PHP to non-web applications but something like what’s being described here where code is transpiled except to a compiled language (like https://github.com/VKCOM/kphp) would be the best bet imo.

We invented a new concept of function colors and implemented it in our KPHP compiler.

Since 2013 we have a php 2 c++ compiler, kphp — it was a hip idea back then, and Facebook had something similar with hiphop

Server side they use kphp (Probably a modified version) https://github.com/VKCOM/kphp

You can also refer to [*PHP vs KPHP vs C++*](https://vkcom.github.io/kphp/various-topics/walk-through-php-kphp-cpp.html).

*[GitHub page](https://github.com/vkcom/kphp)* | *[Web-site (documentation)](https://vkcom.github.io/kphp/)*