Ask HN: Is there every a good reason to create a 1GB+ JSON file?

  • Yep. 3 GB JSON handler reporting in.

    It all depends on what assumptions you can make about update frequency and the continuity of link.

    If you can't assume 100% availability of the link, but you need to maintain operability in between link uptime windows, it's worth paying the price for a sizable data file download, and perform runtime deserialization of that in the abscence of uplink.

    Remember:

    The network being available should never, ever be taken for granted.

  • It makes sense if it's a file of JSON records, one per line Less so, if it's a single blob.

    DOn't forget that JSON isn't only a web interchange format.