> JSON Sucks Does it though? I'm not a huge fan of tools who bash the thing they're trying to help people work with. Maybe "JSON is hard" is a better tag line?
But it isn't. It's dumb, it's annoying, it's overused, but it's not hard.
JSON Hero: Enhanced JSON structure visualization
81–90 of 203 posts
Re: JSON Hero: Enhanced JSON structure visualization
#82My number one requirement for a tool like this is that the JSON content never leaves the machine it's on. I can only imagine the kind of personal information or proprietary internal data that has been unwittingly transmitted due to tools like this. If my objective was to gain the secrets of various worldwide entities, one of the first things I would do is set up seemingly innocent Pastebins, JSON checkers, online fil…
Eric here (one of the creators of JSON Hero) and this is a really good point. We built JSON Hero earlier this year and partly wanted to use it to try out Cloudflare Workers and Remix, hence the decision to store in KV and use that kind of architecture. We're keen to update JSON Hero with better local-only support for this reason, and to make it easier to self-host or run locally.
If the vscode extension did it all locally, I'd 100% install in an instant! DITTO
Re: JSON Hero: Enhanced JSON structure visualization
#83Also, in case you're working in Typescript with a massive JSON and no types: https://quicktype.io/typescript
It generates TS type file from a raw JSON file. Has totally saved my sanity at least once.
Re: JSON Hero: Enhanced JSON structure visualization
#84If we're talking JSON document visualization, it's essential to point out this brilliant page: https://altearius.github.io/tools/json/index.html Was formerly hosted at http://chris.photobooks.com/json
Fantastic, that is far more useful
Re: JSON Hero: Enhanced JSON structure visualization
#85Earlier quoted context omitted.
> My pet gripe is all of the seemingly local (open source) tools that phone home with opt-out metrics, not mentioned in the "getting started" and take some obscure flag to disable and it's just that little bit more complex to do when running the defacto (containerised) build. Exhibit A: DotNet! https://learn.microsoft.com/en-us/dotnet/core/tools/telemetr...
Ouch, this is particularly egregious: "...To opt out, set the DOTNET_CLI_TELEMETRY_OPTOUT environment variable before you install the .NET SDK"
That's only for the telemetry that happens during the install process (if I've read the link correctly). Seems quite reasonable as long as we accept them sending telemetry during install. ("A single telemetry entry is also sent by the .NET SDK installer when a successful installation happens")
For telemetry during actual use, you can set that flag any time, and a message is shown on first use to inform you about it.
So seems relatively reasonable to me.
Re: JSON Hero: Enhanced JSON structure visualization
#86I'm not really clear on what the value-add is here. When is one needing to "visualise" JSON in this way, without editing it? Does it really help that much? Generally I just open in VS Code, reformat and use search etc.
I can think of one valuable use-case: parsing through JSON responses for APIs with poor fields/response documentation -- especially if you have to parse through a ton of information. Still way more readable than XML.
I think this is harder to parse than just having a well formatted structure in a text editor
Re: JSON Hero: Enhanced JSON structure visualization
#87How far from WSDLs and SOAP we’ve come. I applaud this effort. I hate that we’re back to where this feels necessary. I’m not sure if there’s anything better. JSON sure felt better than XML. But did we abstract too far, or did we just get so much better bandwidth and processors, that enriched data exploration is just insignificantly possible? I read the use-cases for this, but I feel like: if you’ve gone so far to whe…
> I read the use-cases for this, but I feel like: if you’ve gone so far to where this is helpful/useful, have you just gone too far?
I don't understand this perspective. JSON isn't used only for RPC, even if that's what most frontend software is doing. For better or worse, it became a data serialization and interchange format - the need for such support tools arises naturally once you're generating or processing anything but most trivial data, and you value your time/sanity.
Re: JSON Hero: Enhanced JSON structure visualization
#88Earlier quoted context omitted.
> My pet gripe is all of the seemingly local (open source) tools that phone home with opt-out metrics, not mentioned in the "getting started" and take some obscure flag to disable and it's just that little bit more complex to do when running the defacto (containerised) build. Exhibit A: DotNet! https://learn.microsoft.com/en-us/dotnet/core/tools/telemetr...
Ouch, this is particularly egregious: "...To opt out, set the DOTNET_CLI_TELEMETRY_OPTOUT environment variable before you install the .NET SDK"
Just to be clear: that is to opt out of the single telemetry message sent by the installer itself on successful install, not to opt out of .NET telemetry in general. You can do that at any time post install by setting the env var, no need to remove and reinstall the entire SDK just to turn off telemetry.
Re: JSON Hero: Enhanced JSON structure visualization
#89If anyone wants to try it out, but doesn't want to send them your Json, here's an example of some real world data https://jsonhero.io/j/t0Vp6NafO2p2
For me, this is harder to use than reading the JSON in a colour text editor such as VSCode. I'm getting less information on the page, and its harder to scan, but that might be because I'm used to reading JSON.
Re: JSON Hero: Enhanced JSON structure visualization
#90Earlier quoted context omitted.
> or a much bigger problem (if it's sensitive personal data). Personal data is a red herring. It's not the only thing that matters. For starters, using this at work with anything not explicitly public is likely a violation of your contract. In some contexts, it may even be gross misconduct or illegal and potentially exposing your employer to large fines. And, in general, I'd say a tool like this that comes without ex…
I agree, mostly. But since when isn’t it obvious that posting data with a browser will send that data somewhere? And the users here are (from what I can tell) developers . I think this is a cool tool for public data and obviously I can’t paste private data sets on any public website, ever.
It's not obvious ever since some of those tools started to blur the line; there are plenty of such little utilities that do everything client-side, or at least claim so. I don't use them with anything but public data, as it takes one mistake or one silent update for the data to get shipped off my machine, but there's a whole generation of devs now who were growing up with webapps and online-first software, so I can easily see some developers making this mistake.
Plus, they offer a VS Code extension. It's not so obvious that it's just the same public website underneath.
Additionally, developers who understand those concerns kind of expect that other developers also understand them, and thus would not create an on-line tool like this in the first place.