geometry-api-java VS plpgsql_check

I programmed with graphical interface in the past in Java, too, which is definitely one of the top choices for me cause it gives the code a lot of structure and makes it easier to maintain and on top of that there exists a lot of community run libraries that might serve my purpose, like this one. I mostly have experience in designing games (SuperMario, Space Invaders and similar) with Java.

It's good software (I've used it more than a decade), however I found GEOS to be a sticking point. When using it on very large polygons, e.g. 10k to 1 million vertices, memory leaks are not uncommon and performance drops off considerably. Debugging SQL -> C -> C++ is not fun and hacking C++ geometry code when it's not part of your normal work is nigh on impossible. I've found the ESRI geometry API for Java to be by far the best geometry API out there. Harder to use initially and obviously JVM specific but faster and more reliable. It's a very good fit for Hadoop / Spark or other JVM applications. Ignore the brand name, I'm not affiliated and it's FOSS with an Apache license.

https://github.com/Esri/geometry-api-java

Finally, while you wait for us to make progress on the Language Server, we’ve added support for linting through the excellent plpgsql_check extension.