Live data from Hacker News

JSON Hero: Enhanced JSON structure visualization

jsonhero.io

161–170 of 203 posts

Re: JSON Hero: Enhanced JSON structure visualization

#161

"JSON Sucks". It really doesn't though.

Not as readable as YAML/TOML. Vastly less if unindented.

More annoying to write than YAML/TOML, no trailing comma. Yes I'd rank it lower than YAML even with its whitespace annoyances, good editor handle that, JSON is still annoying.

Not super compact (althought it's not too bad when compressed).

No proper numeric types, just one "sorta int, sorta float, depends on parser, say farewell to NaNs and infinities", you can't even losslessly transfer a normal IEEE flaot across it.

The schema thing came late so rarely used or supported.

So it really is pretty mediocre all things considered.

Definitely "good enough" but could also be improved.

Re: JSON Hero: Enhanced JSON structure visualization

#162
post #30

Earlier quoted context omitted.

JSON5, and optionally it has trailing commas! It's all I use now.

More on JSON5 is here: https://json5.org/ I like the comments and trailing commas too. It has a few other small improvements as well.

That does address pretty much most of my issues with it.

It's actually good enough to even write configs in it. I do hope it will get enough traction to be standard...

Re: JSON Hero: Enhanced JSON structure visualization

#163
post #48
post #31

My 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.

There are instructions in the readme to 'run locally' - are you saying that even that version (running on localhost:8787) is sending something back to y'all, either from the client in the browser or sending something back via the locally-running server?

I was totally about to clone this repo and run it locally so I can play with some internal json.

Re: JSON Hero: Enhanced JSON structure visualization

#164
post #156

Earlier quoted context omitted.

I worked at a $massive_tech_company_with_extreme_secrecy and using these tools was expressly forbidden because of the risk. Maybe one exists, but I would gladly pay $20 for a Mac app that could do all of this locally: like a Markdown Pro type app but for JSON formatting and validation. I want to simply open the app, paste in some json and have it format it to my requirements (spaces/tabs/pretty/etc.)

I vaguely remember some tool that was just a collection of random tools like that running as local server (including a bunch of crypto primitives) but I can't remember the name now...

You’re probably thinking of the tool made by GCHQ, CyberChef

https://gchq.github.io/CyberChef/

Re: JSON Hero: Enhanced JSON structure visualization

#165
post #156

Earlier quoted context omitted.

I vaguely remember some tool that was just a collection of random tools like that running as local server (including a bunch of crypto primitives) but I can't remember the name now...

You’re probably thinking of the tool made by GCHQ, CyberChef https://gchq.github.io/CyberChef/

Yup, thanks!

Re: JSON Hero: Enhanced JSON structure visualization

#166
> JSON sucks

I don't understand this sentiment at all. Not even sure why we need this tool. Feels like a solution looking for a problem to me.

Personally, the built-in JSON parsing/formatting in VS Code (or any other editor) is plenty for me, and for API results Firefox will automatically format / collapse it.

Eg... open this link in Firefox: https://www.reddit.com/r/funny.json

Re: JSON Hero: Enhanced JSON structure visualization

#167
post #31

My 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…

Better yet, build an operating system and link it to the cloud.

Re: JSON Hero: Enhanced JSON structure visualization

#169
post #155

Earlier quoted context omitted.

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.

It not being opt-in is the problem

If it's not opt-in, the software's spyware, pure and simple, and ought to be lumped in with other malware that should be rejected, shamed, and marginalized until/unless that behavior changes.

I'm sticking to our much-better norms for this shit from c. 2000, damnit! It really is crazy how fast and completely that changed.

Re: JSON Hero: Enhanced JSON structure visualization

#170

Earlier quoted context omitted.

I don’t understand what you mean by JSON was not invented. It was invented by Douglas Crockford. Before he invented JSON, we used XML to pass data around the web. After he invented JSON, it took quite awhile to catch on. There were many years of transition where some web services would only send xml and others could send xml or json. Eventually all web services gave you the choice of which one it would send. And then…

> I don’t understand what you mean by JSON was not invented. It was invented by Douglas Crockford. Douglas Crockford took his time to write up a specification for the JavaScript Object Notation (JSON). That specification is, quite literally, "based on a subset of the JavaScript Programming Language Standard ECMA-262 3rd Edition - December 1999." It's in the name. There is no way around this. MDN's doc on JavaScript's…

I don’t think that means it was not invented. Otherwise we would have had it years before. What I understand “based on a subset of JavaScript” to mean is, Crockford chose some of the JS data types (object, array, number, string) and invented a string representation of them that could be used as a data interchange format. That was revolutionary. I remember when I first learned about JSON. It felt like Crockford was a genius for coming up with it, and then wondering why nobody else had come up with it before him. There is no way we would have suffered through XML Hell for so many years I’d there had been another option. But there wasn’t another option. Why? Because Crockford hadn’t invented JSON yet.
Post reply on HN