jzon
jsonstreamingparser
| jzon | jsonstreamingparser | |
|---|---|---|
| 8 | 3 | |
| 137 | 734 | |
| - | 1.0% | |
| 7.2 | 1.8 | |
| about 1 month ago | 10 months ago | |
| Common Lisp | PHP | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jzon
-
Common Lisp JSON parser?
jzon https://github.com/Zulu-Inuoe/jzon/ is the newest and probably the most complete, the most robust and the most accurate. It explains everything in its readme. I have settled on Shasht so far.
-
How to create a post body for dexador
I think the consensus now for JSON libraries (it's a meme that there are way too many CL JSON libraries) is to use jzon (https://github.com/Zulu-Inuoe/jzon). It's the best one I've found.
-
SBCL Help wanted: capturing big stdout (100M) and json parsing
I use JZON for SAX-style parsing; it works very well. If you can arrange to read your input as a stream, you shouldn't have memory problem with the reading/parsing part of your project.
- JZON hits 1.0 and is at last on the latest QL release: a correct and safe JSON parser, packed with features, and also FASTER than the latest JSON library advertised here.
- What was your favorite Common Lisp release (implementation, library, tool, ...) in 2021?
- jzon - a correct and safe JSON parser.
jsonstreamingparser
-
OPML Is Underrated
Yes and no. You are correct about it being a document protocol, but it has long been set up as a big document protocol.
Most XML libraries are structured to receive XML in packets, in asynchronous bursts. I don't know of many JSON handlers that can do the same. They do exist (I use one, in the backend of one of my projects[0]), but they aren't as common. XML has packet/async built into OS SDKs, but JSON tends to be "The Whole Nine Yards" handling.
With Big Data/ML, I'm surprised that this is still a thing.
[0] https://github.com/salsify/jsonstreamingparser
-
SBCL Help wanted: capturing big stdout (100M) and json parsing
In other languages, you generally wouldn't want to load super large JSON files all at once into memory as it uses a crapton of heap space, often creates far too many unnecessary objects, etc. Often you'd do a streaming parser of some kind, essentially discarding parts of the doc after you've processed them. For example (sorry for the dirty PHP link here, but it illustrates the concept): https://github.com/salsify/jsonstreamingparser/
-
PHP RFC: Working With Substrings
There are few cases where such functions would be useful and could bring real impact. For example if you have to write custom JSON parser (and sometimes you have to - when working with large objects you simply could not have memory to store everything) you process strings often and byte by byte - then such improvements really could matter. And processing large json files is not uncommon task: https://github.com/salsify/jsonstreamingparser
What are some alternatives?
clog - CLOG - The Common Lisp Omnificent GUI
json-streams - Common Lisp library for reading and writing JSON.
jingo - This package provides the ability to encode golang structs to a buffer as JSON very quickly.
kandria - A post-apocalyptic actionRPG. Now on Steam!
lem - Common Lisp editor/IDE with high expansibility
jsondiff - Compute the diff between two JSON documents as a series of RFC6902 (JSON Patch) operations
clingon - Command-line options parser system for Common Lisp
jonathan - JSON encoder and decoder.
emerald - Simple JSON serializer/deserializer for Dart (only JIT, not Flutter).
cl-json-pointer - JSON Pointer processor for Common Lisp
access - A common lisp library to unify access to common dictionary-like data-structures