<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>SamMakesCode</title>
    <link>https://sammakescode.writeas.com/</link>
    <description></description>
    <pubDate>Wed, 16 Sep 2026 18:11:12 +0000</pubDate>
    <item>
      <title>Devlog: Why did I bother with SPAs?</title>
      <link>https://sammakescode.writeas.com/test-post?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[I started with programming in PHP around 2007. It was a shit-show back then (though it’s much better now). As the internet evolved and websites became more complex and responsive we had to start using Javascript.&#xA;&#xA;Facebook did it, so we didn’t have a choice. Initially it was just to move elements around, submit forms and spy on our users.&#xA;&#xA;But, pretty soon we were separating our apps into front-end and back-end. This added considerable development time, but it was worth it because if you ever wanted an app, it was easier to integrate. That’s not a bad argument. I often did want an app.&#xA;&#xA;Now, in order to be competitive in search engines we have to markup our sites with OpenGraph and Schema.org. Which, don’t get me wrong, isn’t a bad thing. Telling search engines what the relevant information on your page is without them having to make educated guess is a good thing.&#xA;&#xA;BUT, search engines try not to load the Javascript of a site if they can help it. If your site 100% relies on Javascript on the front-end, search engines are slow to update it and content aggregators such as Twitter and Facebook won’t even run the Javascript.&#xA;&#xA;We’ll have to rely on Google’s SEO for now and then go back to server-side rendering with Javascript mini-apps with v2.&#xA;&#xA;For fuck sake.]]&gt;</description>
      <content:encoded><![CDATA[<p>I started with programming in PHP around 2007. It was a shit-show back then (though it’s much better now). As the internet evolved and websites became more complex and responsive we <em>had</em> to start using Javascript.</p>

<p>Facebook did it, so we didn’t have a choice. Initially it was just to move elements around, submit forms and spy on our users.</p>

<p>But, pretty soon we were separating our apps into front-end and back-end. This added considerable development time, but it was worth it because if you ever wanted an app, it was easier to integrate. That’s not a bad argument. I often did want an app.</p>

<p>Now, in order to be competitive in search engines we have to markup our sites with OpenGraph and Schema.org. Which, don’t get me wrong, isn’t a bad thing. Telling search engines what the relevant information on your page is without them having to make educated guess is a <em>good</em> thing.</p>

<p>BUT, search engines try not to load the Javascript of a site if they can help it. If your site 100% relies on Javascript on the front-end, search engines are slow to update it and content aggregators such as Twitter and Facebook won’t even run the Javascript.</p>

<p>We’ll have to rely on Google’s SEO for now and then go back to server-side rendering with Javascript mini-apps with v2.</p>

<p>For fuck sake.</p>
]]></content:encoded>
      <guid>https://sammakescode.writeas.com/test-post</guid>
      <pubDate>Wed, 21 Dec 2022 11:13:31 +0000</pubDate>
    </item>
  </channel>
</rss>