deploy: 2a008fa

Author: cekrem

index.xml

@@ -6,8 +6,16 @@
     <description>Recent content on cekrem.github.io</description>
     <generator>Hugo</generator>
     <language>en-us</language>
-    <lastBuildDate>Wed, 17 Dec 2025 00:00:00 +0000</lastBuildDate>
+    <lastBuildDate>Fri, 19 Dec 2025 00:00:00 +0000</lastBuildDate>
     <atom:link href="https://cekrem.github.io/index.xml" rel="self" type="application/rss+xml"/>
+    <item>
+      <title>Elm on the Backend with Node.js: An Experiment in Opaque Values</title>
+      <link>https://cekrem.github.io/posts/elm-on-the-backend-with-nodejs/</link>
+      <pubDate>Fri, 19 Dec 2025 00:00:00 +0000</pubDate>
+      <guid>https://cekrem.github.io/posts/elm-on-the-backend-with-nodejs/</guid>
+      <description><![CDATA[<p>What if you could write backend logic in Elm? Not &ldquo;Elm-like&rdquo; or &ldquo;inspired by Elm&rdquo; – actual Elm, with the compiler, the types, the whole package. I&rsquo;ve been nerd-sniped by this idea for a while, and last night I finally sat down to build a proof of concept.</p>
+<p><strong>Disclaimer:</strong> This is me experimenting with a concept, not suggesting anyone <em>should</em> do this. If you actually want Elm on the backend, <a href="https://lamdera.com/" class="external-link" target="_blank" rel="noopener">Lamdera</a> does something far more sophisticated – it&rsquo;s a full platform with seamless frontend/backend Elm, automatic persistence, and real deployment story. My thing is&hellip; not that. It&rsquo;s just a hack to see what&rsquo;s possible with vanilla Node.js and vanilla Elm, nothing more.</p>]]></description>
+    </item>
     <item>
       <title>TypeScript Goes Go: What Does This Mean for Us?</title>
       <link>https://cekrem.github.io/posts/typescript-goes-go/</link>

minified.xml

@@ -1,4 +1,5 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>cekrem.github.io</title><link>https://cekrem.github.io/</link><description>Recent content on cekrem.github.io</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 17 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://cekrem.github.io/index.xml" rel="self" type="application/rss+xml"/><item><title>TypeScript Goes Go: What Does This Mean for Us?</title><link>https://cekrem.github.io/posts/typescript-goes-go/</link><pubDate>Wed, 17 Dec 2025 00:00:00 +0000</pubDate><guid>https://cekrem.github.io/posts/typescript-goes-go/</guid><description>&lt;p&gt;Anders Hejlsberg announced that Microsoft is porting TypeScript to Go. Yes, &lt;em&gt;that&lt;/em&gt; Go. Not Rust (which everyone expected), not C++ (which would be reasonable), but Go.&lt;/p&gt;
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>cekrem.github.io</title><link>https://cekrem.github.io/</link><description>Recent content on cekrem.github.io</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 19 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://cekrem.github.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Elm on the Backend with Node.js: An Experiment in Opaque Values</title><link>https://cekrem.github.io/posts/elm-on-the-backend-with-nodejs/</link><pubDate>Fri, 19 Dec 2025 00:00:00 +0000</pubDate><guid>https://cekrem.github.io/posts/elm-on-the-backend-with-nodejs/</guid><description>&lt;p&gt;What if you could write backend logic in Elm? Not &amp;ldquo;Elm-like&amp;rdquo; or &amp;ldquo;inspired by Elm&amp;rdquo; – actual Elm, with the compiler, the types, the whole package. I&amp;rsquo;ve been nerd-sniped by this idea for a while, and last night I finally sat down to build a proof of concept.&lt;/p&gt;
+&lt;p&gt;&lt;strong&gt;Disclaimer:&lt;/strong&gt; This is me experimenting with a concept, not suggesting anyone &lt;em&gt;should&lt;/em&gt; do this. If you actually want Elm on the backend, &lt;a href="https://lamdera.com/" class="external-link" target="_blank" rel="noopener"&gt;Lamdera&lt;/a&gt; does something far more sophisticated – it&amp;rsquo;s a full platform with seamless frontend/backend Elm, automatic persistence, and real deployment story. My thing is&amp;hellip; not that. It&amp;rsquo;s just a hack to see what&amp;rsquo;s possible with vanilla Node.js and vanilla Elm, nothing more.&lt;/p&gt;</description></item><item><title>TypeScript Goes Go: What Does This Mean for Us?</title><link>https://cekrem.github.io/posts/typescript-goes-go/</link><pubDate>Wed, 17 Dec 2025 00:00:00 +0000</pubDate><guid>https://cekrem.github.io/posts/typescript-goes-go/</guid><description>&lt;p&gt;Anders Hejlsberg announced that Microsoft is porting TypeScript to Go. Yes, &lt;em&gt;that&lt;/em&gt; Go. Not Rust (which everyone expected), not C++ (which would be reasonable), but Go.&lt;/p&gt;
 &lt;p&gt;I&amp;rsquo;ll admit my first reaction was a grin. Go is one of those languages I genuinely enjoy working with - simple, pragmatic, fast. My second reaction was &amp;ldquo;wait, 10x faster?&amp;rdquo; And my third was &amp;ldquo;okay, this makes a lot of sense actually.&amp;rdquo;&lt;/p&gt;
 &lt;h2 id="the-numbers"&gt;
  The Numbers