cyanide
json
Our great sponsors
cyanide | json | |
---|---|---|
9 | 41 | |
11 | 4,537 | |
- | 2.6% | |
3.2 | 8.8 | |
10 months ago | 11 days ago | |
Elixir | Rust | |
Apache License 2.0 | Apache License 2.0 |
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.
cyanide
-
Would you recommend JSON/CSV/Other for data storage in games?
No, it stands for "Binary JSON".
-
What is MongoDB ?
BSON specification
-
MUON: Compact and simple binary format, that uses gaps in Unicode encoding for markup
I recommend looking at https://ubjson.org and https://bsonspec.org , this will answer most of your questions.
-
I need a json file that includes all or most of the data types supported by MongoDB.
or https://bsonspec.org/
-
Minimizing the size of JSON by using CodingKey
BJSON Binary JSON, with a Swift Library here and should be one for your other end
-
Basics of MongoDB
Starting this tutorial we specified that data in MongoDB is stored in collections. We also specified that in MongoDB we use syntax similar to JSON. That syntax is called "Binary JSON" or BSON. BSON is similar to JSON; but it's more like an encoded serialization of JSON. We can find useful information in the BSON website.
-
It's Time to Retire the CSV
> I'm saying that when you decode an Avro document, the result that comes out (presuming you don't tell the Avro decoder anything special about custom types your runtime supports and how it should map them) is a JSON document.
Semantic point: it's not a "document".
There are tools which will decode Avro and output the data in JSON (typically using the JSON encoding of Avro: https://avro.apache.org/docs/current/spec.html#json_encoding), but the ADT that is created is by no means a JSON document. The ADT that is created has more complex semantics than JSON; JSON is not the canonical representation.
> By which I don't mean JSON-encoded text, but rather an in-memory ADT that has the exact set of types that exist in JSON, no more and no less.
Except Avro has data types that are not the exact set of types that exist in JSON. The first clue on this might be that the Avro spec includes mappings that list how primitive Avro types are mapped to JSON types.
> Or, to put that another way, Avro is a way to encode JSON-typed data, just as "JSON text", or https://bsonspec.org/, is a way to encode JSON-typed data
BSON, by design, was meant to be a more efficient way to encode JSON data, so yes, it is a way to encode JSON-typed data. Avro, however, was not defined as a way to encode JSON data. It was defined as a way to encode data (with a degree of specialization for the case of Hadoop sequence files, where you are generally storing a large number of small records in one file).
A simple counter example: Avro has a "float" type, which is a 32-bit IEEE 754 floating point number. Neither JSON nor BSON have that type.
Technically, JSON doesn't really have types, it has values, but even if you pretend that JavaScript's types are JSON's types, there's nothing "canonical" about JavaScript's types for Avro.
Yes, you can represent JSON data in Avro, and Avro in JSON, much as you can represent data in two different serialization formats. Avro's data model is very much defined independently of JSON's data model (as you'd expect).
-
Sending 😀 in Go
For me, this exploration started when I was attempting to improve handling of Unicode surrogate pair values in the MongoDB Go driver's Extended JSON unmarshaler. The Extended JSON format is an extension to the standard JSON format that adds type information and allows deterministic conversion to and from BSON.
json
-
What even is a JSON number?
Oh wow. So serde_json doesn't roundtrip floats by default, it uses some imprecise faster algorithm https://github.com/serde-rs/json/issues/707
Good thing there's msgpack I guess.
-
I pre-released my project "json-responder" written in Rust
tokio / hyper / toml / serde / serde_json / json5 / console
-
Flow Updater JSON Creator
Serde JSON, an extension of the serde crate that enables the serialization and deserialization of Rust structs.
-
A Simple CRUD API in Rust with Cloudflare Workers, Cloudflare KV, and the Rust Router
To serialize and deserialize data, we'll employ the popular serde crate along with serde_json. This will allow us to easily convert between Rust types and JSON when working with API requests and responses. For async operations we'll use the Rust futures crate.
- Rust devs push back as Serde project ships precompiled binaries
-
Building a Rust app with Perseus
From the Cargo.toml file above, we can see that the Perseus version at the time of publication is 0.4.2 and has the following dependencies that are common to both the engine side (server-side) and client side of a Perseus application: sycamore, serde, and serde_json.
-
REST API in RUST with ntex
serde_json
-
Müsli - An experimental binary serialization framework with more choice
Number parsing uses a fairly naive but uses a lossless algorithm in musli-json. In serde_json they use a fork of lexical I haven't wrapped my head around. I wanted something simple to start with.
-
How can I deserialise this value?
Your best best would be to use an enum. Either your own or something like the one from serde_json depending on what you are trying to do.
-
Spotting and Avoiding Heap Fragmentation in Rust Apps
Don't do that if you care about memory usage. In your toy program, I wouldn't be surprised if memory usage was a lot better if you used Box instead. (even if it doesn't look like it, you can handle almost all the use cases of serde_json::Value with it, often not much less convenient)
What are some alternatives?
BSONMap - Elixir package that applies a function to each document in a BSON file.
serde - Serialization framework for Rust
naya - A fast streaming JSON parser written in Python
json-rust - JSON implementation in Rust
json - JSON for Modern C++
hjson-rust for serde - Hjson for Rust
ndjson.github.io - Info Website for NDJSON
pikkr - JSON parser which picks up values directly without performing tokenization in Rust
csvz - The hot new standard in open databases
serde-yaml - Strongly typed YAML library for Rust
Mongoose - MongoDB object modeling designed to work in an asynchronous environment.
RapidJSON - A fast JSON parser/generator for C++ with both SAX/DOM style API