<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Purego on Cesar Gimenes</title><link>https://crg.eti.br/en/tags/purego/</link><description>Recent content in Purego on Cesar Gimenes</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>crg@crg.eti.br (Cesar Gimenes)</managingEditor><webMaster>crg@crg.eti.br (Cesar Gimenes)</webMaster><lastBuildDate>Mon, 22 Jun 2026 10:15:00 -0300</lastBuildDate><atom:link href="https://crg.eti.br/en/tags/purego/index.xml" rel="self" type="application/rss+xml"/><item><title>Glaze, a Desktop WebView in Go Without CGO</title><link>https://crg.eti.br/en/post/glaze/</link><pubDate>Mon, 22 Jun 2026 10:15:00 -0300</pubDate><author>crg@crg.eti.br (Cesar Gimenes)</author><guid>https://crg.eti.br/en/post/glaze/</guid><description>&lt;p>Opening a window with HTML in Go almost always charges a toll in C.&lt;/p>
&lt;p>Either you turn on cgo and drag a C toolchain into the project, or someone embeds a compiled &lt;code>.dll&lt;/code>/&lt;code>.so&lt;/code>/&lt;code>.dylib&lt;/code> in the binary and extracts it to disk on first run. Both work. And both take away exactly what I like about the ecosystem: the &lt;code>go build&lt;/code> that cross-compiles to three systems without a second thought, the reproducible build, the &lt;code>go install&lt;/code> that works for anyone who cloned the repo. It&amp;rsquo;s the first thing that goes the moment C enters the picture.&lt;/p></description></item></channel></rss>