Hello,
I would like to start working on GeoJSON (and it's extensions json-fg,
dggrs, ...) but before that I would like to talk about the current
choice of JSON library made.
So far we have the CoverageJSON module (which I wrote), this module use
Jakarta JSON-B v3.
It works but JSON-B has not been adopted by the community.
The first version of JSON-B (JSR 367) was out in 2017. after the
creation of JackartaEE by Eclipse (when JavaEE stopped), two new
versions of JSON-B came out.
But even today, we only have Eclipse Yasson (the reference
implementation) which exist to promote JSON-B.
The truth is the Jackson-json library exist since 2016 and has a full
api very similar to json-p and json-b.
the project is very active and has large support for other json-like
formats such as : avro, cbor, ion, protobuf, smile, ... and more...
By looking at maven repo of the two projects :
https://mvnrepository.com/artifact/org.eclipse/yasson
https://mvnrepository.com/artifact/com.fasterxml.jackson.core/jackson-databind
We can see jackson is clearly the winner.
My feeling is we are going the wrong way, I understand sticking to JRE
API and big project API is a security.
But even if the community wakes up and build around json-b starting
today, it would take a decade before it catch up with jackson-json.
Does anyone have objections to switching to jackson-json ?
Johann Sorel
