In the last two posts, I talked about the improvements to JsonPointer.Net and some of the memory management tools I used to enact those improvements. In this post, I’d like to start talking about ...

Last time, I took you through the developer’s journey I had while updating JsonPointer.Net and how taking time to really consider my new architecture resulted in completely overhauling the library ...

This post was going to be something else, and somewhat more boring. Be glad you’re not reading that. In the midst of updating JsonPointer.Net, instead of blindly forging on when metrics looked de...

Holy performance increase, Batman! I recently made an update to JsonLogic.Net that cut run times and memory usage in half! In half?! Yes! Here’s the benchmark: Method Coun...

Some time ago, I released my first attempt at code generation from JSON Schemas. However, I’ve decided to deprecate the library in favor of Corvus.JsonSchema. When I created JsonSchema.Net.CodeGe...

I don’t even know how to begin this post. I don’t think there has been as big an announcement for this project as support for .Net 8 and Native AOT. Yet here we are. HUGE thanks to Jevan Saks fo...

Both of the vocabularies defined by json-everything are getting a facelift. The data vocabulary is getting some new functionality. The UniqueKeys vocabulary is being deprecated in favor of th...

JSON-e is a data-structure parameterization system for embedding context in JSON objects. At least that’s how they describe it. My take would be that it’s something of an amalgamation between...

I’ve discovered another odd consequence of what is probably fully intentional code: 4m != 4.0m. Okay, that’s not strictly true, but it does seem so if you’re comparing the values in JSON. var a ...

Cross-posting from the JSON Schema Blog. I’ve received a lot of questions (and purported bugs) and had quite a few discussions over the past few years regarding JSON Schema output, and by far the ...