<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Native on cekrem.github.io</title><link>https://cekrem.github.io/tags/native/</link><description>Recent content in Native on cekrem.github.io</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 08 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://cekrem.github.io/tags/native/index.xml" rel="self" type="application/rss+xml"/><item><title>Native Elm (the real kind this time)</title><link>https://cekrem.github.io/posts/native-elm/</link><pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate><guid>https://cekrem.github.io/posts/native-elm/</guid><description>&lt;p&gt;Back in December I &lt;a href="https://cekrem.github.io/posts/elm-on-the-backend-with-nodejs/" &gt;hacked Elm onto a Node.js backend&lt;/a&gt; and got a little carried away calling it &amp;ldquo;Elm on the backend.&amp;rdquo; It wasn&amp;rsquo;t, really. Node did all the actual work &amp;ndash; opened the socket, parsed the HTTP, wrote the response &amp;ndash; and Elm sat in the middle shuffling opaque values between ports. A fun trick, and I still think the passport-through-Elm bit is neat. But the whole time, there was a JavaScript runtime underneath holding the thing up.&lt;/p&gt;</description></item></channel></rss>