4 ms·
It's still a shame that Excel's JSON support is so good, but no business user trusts it because "you can't double click the files" and CSV remains the worst bes
by WorldMaker 3y ago
It's still a shame that Excel's JSON support is so good, but no business user trusts it because "you can't double click the files" and CSV remains the worst best thing you can double click.
I don't want Excel to take over the file association for .json but I do sometimes wish Excel would just invent a file extension like .xljson that loads JSON so that at least you could trivially rename a JSON file to .xljson and get working double-click for your business users but a file format (with optional schema support even) that's a more modern and saner de facto standard than CSV.
I think that one dumb trick would improve everyone's productivity a great deal.
- imtringued 3y agoYou're talking about users of an operating system that hides file extensions by default.
- WorldMaker 3y agoNo, I'm talking about developing for those users. Right now if you want to write the simplest, dependency lightest export code that those users can double-click and open in Excel you are writing yet another CSV export. It would be nice if instead you could take an existing API that returns JSON and wrap it in a mimetype like application/json+excel, and add a Content-Disposition: attachment; filename=thisapi.xljson and get Excel double-click support without another flaky CSV file.