Looks cool, but imo if some json is big enough that you need a dedicated tool to read it it should be in a database, and if it's small enough that it shouldn't be in a database it's small enough to understand and edit raw. What use cases are you using this editor for?
Not every json file needs a full database, sometimes you just got config files, translation files, mock data, stuff like that which is big enough to be annoying in vscode but not worth setting up postgres. The column drill-down looks handy for that kind of data Also like the diff before save feature, i lost count of how many time i accidentally messed up a json structure in the past