Duplicated efforts?

For me, this module is actually working (after using the patch from https://www.drupal.org/node/2656580), unlike JSONB which was a total fail for me using MariaDB...

I'd prefer the DB storage using JSON directly instead of serializing the object, but at least it is working.

To be honest, JSON field should be in core (with and/or without serialization) because of the direction D8 is taking with support of JSON pretty much everywhere.

Hopefully this module can reach stable status soon since it is working great for those of us having issues with JSONB.

Given that I was granted comaintainer access to both modules in the past 24 hours (!), I'd be delighted to see this happen.

I actually think json_field would be a better location for the functionality, given the modules are about a *field* as opposed to something else.

Looking at this module's code.. it doesn't seem to actually use native JSON fields, right? It seems to be a wrapper that just uses text fields of various sizes?

Yes, this module serializes and and stores text in the DB since the dev had to meet minimum D8 requirements. The other one stores as JSON type. I think it would be great to have JSON storage for those that support it, and fallback to serialization.

Maybe it would be better to create a way for a "JSON field" to just attach to all other entities? For example, an node/term or image upload with JSON attached for advanced config. The individual (CCK) field would be based on that (entity reference).

Currently, I am preprocessing the field parsed from the output of this module into the twig template and not printing that field.

I'm going to work on porting over the functionality from JSONB, starting with #2880415: Add support for JSON and JSONB database field types.

Is this still active or dying slowly? Because I feel like this is a very sweet way to handle data instead of php serialization. I see there are 2 solid patches that still needed review after a few months, which both were some small changes.

Reviewed them BTW and they are good to go.

But what are the plans from the maintainers, is this something that will still be maintained?

I haven't had to use this in a while, but I still think it's important.

Lets work out what needs to be committed for a 1.0 release and we'll work towards it.