JSON columns are very useful in some circumstances but you shouldn’t use them as a replacement for a database schema, and if I’m honest I’m yet to see anyone truly suggest that.
I use schema for everything relational, and put everything else (all the nice-to-know data) in JSONB. Works really well. Stacks like Rails lean into this with `store_accessor` which lets you designate a JSON column as storage for arbitrary data that looks and feels like a separate column.
I hope not. JSON columns purge all the good things a relational database offers and keeps the SQL. It is the worst of every option.
That really should be the opposite of the NoSQL experience. Disbarred by the fact that SQL is involved.