Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Approximately everything, but on its own nothing. Serde provides the framework and macros/annotations, serde_json is the "backend" implementing the actual json serialization.

Sure, it could be named serde_framwork and serde_json, but I think serde and serde_json isn't that bad either.



sort by: page size:

Interesting page through it... just a series of schema-less JSON files. Already some support in there for important stuff; ex: logback

Finally I'll switch to Serde JSON :) I use beta and beta is 1.9 today, with awesome features stabilized!

I really love Serde, but one consequence of splitting out the formats into different libraries is that different formats can be of substantially different levels of quality. My impression is that JSON support is best-of-class, but I have no idea about the others.

For example, I've been looking at the CBOR library for Serde [1], and it's not obvious whether the library is full-featured, robust, actively supported, etc. Same goes for many of the other Serde formats. At the moment I'm likely to just choose JSON for new projects since I don't want to build on top of something that isn't known to be solid, but it would be really nice to be able to use binary formats for what I want to do.

Now that Serde is 1.0 it would be nice to do a push on the individual formats so that users coming in can tell what's active and well-supported vs a (possibly inactive) community contribution.

[1]: https://github.com/pyfisch/cbor


It's a JSON store and libraries to support access to it. Plus ability to set up users and push messages and maybe a couple of other things.

It has everything to do with JSON. It's a REST client that produces UI elements using a JSON-like hypermedia type.

Gotcha!

FWIW, serde_json makes it very easy; if you were doing it yourself, I can see how it'd be harder :)

The second edition of the book's ownership and borrowing chapters go into String vs &str in great detail, if you want to become super sharp :)

(and yeah, we agree that the lifetime annotation isn't very nice looking, but every alternative we tried looked worse.)


Yeah, basically the json parsers and generators and the programs that use them seem to have settled on implementations that mostly work together.

Despite it's name, Jsonnet can generate JSON, YAML, INI, and other formats.

Out of curiosity, what JSON library was that?

Yes, it does. The frontend and the backend only speak JSON.

The language is just JSON with functions. It's actually so nice to write configurations in that I wish it was more easier to use as a standalone thing.

The author does mention JSON5 which implements all of those features.

That's a pretty cool project. But I wonder what to do with it. If I understand correctly, it transforms the JSON into a format that's easier to parse yourself.

Personally, I use jq and it has a built-in query language of some sorts.


I've used it for a few small tools and love it. I started out just writing schemas for testing the format of JSON generated by tools or pulled from an API, but you can do so much more... like using it to generate documentation or even [create forms](https://github.com/joshfire/jsonform).

It uses the JSON API.

And a small number of tools for composing JSON.

I'm happy with json5 for now, it addresses my complaints with json and is supported by the main tools I use.

IIRC there is a JSON6 format which adds features and improvements on top of JSON5.

whoa, thanks, didn't know about json support, super useful!
next

Legal | privacy