<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Svelte on The Writings</title><link>https://blog.gs-101.dev/tags/svelte/</link><description>Recent content in Svelte on The Writings</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 24 Oct 2026 11:59:00 -0300</lastBuildDate><atom:link href="https://blog.gs-101.dev/tags/svelte/index.xml" rel="self" type="application/rss+xml"/><item><title>Markdown Oriented Programming</title><link>https://blog.gs-101.dev/posts/markdown-oriented-programming/</link><pubDate>Sat, 24 Oct 2026 11:59:00 -0300</pubDate><guid>https://blog.gs-101.dev/posts/markdown-oriented-programming/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;In which we analyse a solution to the &lt;a href="https://htmx.org/essays/locality-of-behaviour/"&gt;Locality of Behaviour&lt;/a&gt; question from the subconscious.&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;It was revealed to me in a dream.&lt;/p&gt;&#10;&lt;p&gt;Epic Games (who suddenly had a web engineering blog) published a post about a store revamp and a new repository model they invented for it.&lt;/p&gt;&#10;&lt;p&gt;In the &amp;ldquo;Traditional&amp;rdquo; repository model, implementation details such as placement, functionality and looks are scattered through the repo. In this &amp;ldquo;New and Improved&amp;rdquo; model, Epic managed to separate everything into individual components, so trying to build a mental model around the codebase was simple.&lt;/p&gt;</description></item></channel></rss>