<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Json on cekrem.github.io</title><link>https://cekrem.github.io/tags/json/</link><description>Recent content in Json on cekrem.github.io</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 06 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://cekrem.github.io/tags/json/index.xml" rel="self" type="application/rss+xml"/><item><title>Go 1.27: encoding/json/v2, Stricter Defaults, and Finally [] for Nil Slices</title><link>https://cekrem.github.io/posts/go-json-v2-finally-says-no/</link><pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate><guid>https://cekrem.github.io/posts/go-json-v2-finally-says-no/</guid><description>&lt;p&gt;The Go team &lt;a href="https://go.dev/blog/jsonv2" class="external-link" target="_blank" rel="noopener"&gt;just shipped &lt;code&gt;encoding/json/v2&lt;/code&gt;&lt;/a&gt; as stable in Go 1.27. It&amp;rsquo;s been available behind &lt;code&gt;GOEXPERIMENT=jsonv2&lt;/code&gt; since 1.25, and I&amp;rsquo;ve been meaning to try it ever since (I never got around to it). So now I finally did.&lt;/p&gt;&#10;&lt;p&gt;First of all: I have some mixed feelings about &lt;code&gt;encoding/json&lt;/code&gt;. It works fine most of the time, but it also accepts quite a lot of stuff it shouldn&amp;rsquo;t, without telling you. Coming from Elm, where a decoder fails the moment something doesn&amp;rsquo;t match, v1 always felt a bit too forgiving for my taste. v2 is a lot stricter, and I like it!&lt;/p&gt;</description></item></channel></rss>