Huh
JSON Hero: Enhanced JSON structure visualization
71–80 of 203 posts
Re: JSON Hero: Enhanced JSON structure visualization
#72My 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…
This reminds me of an "Online HTML Minifier" website that analyzed the text and included affiliate links for random words within the text.
And they operated for years, when someone noticed links on their own website, they haven't added themselves and tried to figure out, how it happened, because nobody else had access to the website.
(Will update with a link, if I find it.)
Re: JSON Hero: Enhanced JSON structure visualization
#73I just want JSON with comments. I don't want YAML.
Then you'll want to look into JSONC.
Re: JSON Hero: Enhanced JSON structure visualization
#74The first thing I see when I go to the site: JSON SUCKS Uh... It does? I remember when XML was the main data interchange format of the web. That sucked. JSON is amazing, terrific, wonderful, etc. in comparison.
> I remember when XML was the main data interchange format of the web. That sucked. I wonder why - apart from the "Should this be an element or an attribute?" issues and oddities in various implementations, XML doesn't seem like the worst thing ever. Actually, in a web development context, I'd argue that WSDL that was used with SOAP was superior to how most people worked with REST (and how some do), since it's taken…
For me, it is because I can do JSON.parse() and boom, it is plain JavaScript objects, arrays, strings, etc. XML was never that simple.
Re: JSON Hero: Enhanced JSON structure visualization
#75Earlier quoted context omitted.
It's always strange to think that we went through formats like XML (and even earlier, XDR) before inventing something as seemingly simple and obvious as JSON.
Why does React use JSX when it could be all JavaScript and JSON? My guess is that XML is good for situations where text and data is mixed.
because separating attributes and child elements is actually useful in that context. better matches the Dom. and we need the power of js to do stuffs.
Re: JSON Hero: Enhanced JSON structure visualization
#76My 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…
I agree.
My tool flatterer: https://lite.flatterer.dev/ converts deeply nested JSON to csv/xlsx, is done in web assembly in the browser.
It hard to prove that it is not sending data to a server, so it can be trusted. I know people could check dev tools but that is error prone and some users may not be able to do it.
I wish there was an easy way to prove this to users as it would make online tools like this much more attractive.
Re: JSON Hero: Enhanced JSON structure visualization
#77Earlier quoted context omitted.
the extension apparently can be configured to use a locally running instance of the server. But yes, by default it uses the remote version, and thus you post publicly the json, which may or may not be ideal depending on what you're doing.
"the extension apparently can be configured to use a locally running instance of the server" - well that sounds needlessly complicated, I mean, the code could be implemented directly in the extension (I know, that's probably easier than it sounds if you are trying to maintain both the extension and the online version with the same code base). "you post publicly the json, which may or may not be ideal depending on wha…
> 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 explicit, bold warning that it's shipping data off your machine, is just being rude.
Re: JSON Hero: Enhanced JSON structure visualization
#78My 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!
Re: JSON Hero: Enhanced JSON structure visualization
#79Earlier quoted context omitted.
"the extension apparently can be configured to use a locally running instance of the server" - well that sounds needlessly complicated, I mean, the code could be implemented directly in the extension (I know, that's probably easier than it sounds if you are trying to maintain both the extension and the online version with the same code base). "you post publicly the json, which may or may not be ideal depending on wha…
> 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.
Re: JSON Hero: Enhanced JSON structure visualization
#80Earlier quoted context omitted.
jsoncrack cannot even open the simpliest of my json files (600K: too large), whilst this handled it easily.
what is the use case for having 600K (lines? bytes?) JSON? I'm a bit shocked and curious at the same time :)
Data dumps and exports between systems. REST APIs, databases, that sort of thing. CSV is the most common utf8/ascii option.