Please make your products work with URLs
Author here. Sorry for those having trouble viewing the site. That&#x27;s obviously never the intention. The current incarnation is actually a bit of an experiment. Unfortunately, my blog is only occasionally tested against front page traffic so I don&#x27;t always get a feel for what&#x27;s not working.<p>That said, I assure you I am intimately familiar with the tradeoffs of different methods of delivering HTML. TL;DR it&#x27;s my personal site and I&#x27;ll do what I want with it. It&#x27;s for fun. The previous version of this site used a static site generator I wrote myself[0]. I switched to client-side JS rendering for several reasons.<p>First, having a build step creates a dependency on both the build tool and a specific action. If you clone my blog[1] (with submodules) you should be able to host it exactly as-is from the repo. No build step required. I hold a fairly extreme view[2] on dependencies.<p>Second, I wanted user interactions within my site to be very fast[3]. After the initial load, subsequent navigations are much faster (and consistent) than retrieving a new static HTML page. Obviously once the HTML is cached that&#x27;s no longer true, but I&#x27;m optimizing for first-time visitors. Though I should give more consideration to the fact that most of you are only going to look at the one linked page.<p>Also, I plan to eventually add some quirky little things to the site which require maintaining state between navigations. For example, I thought it would be fun to integrate a little 2D adventure game with a character you can move around to scroll the content.<p>EDIT: I should also acknowledge that while I defend the use of JS on my site, I concede that supporting non-JS use cases would be far more true to supporting &quot;the simple case&quot; as fallback. Simply supporting browsers in the default configuration isn&#x27;t a very high bar. Browsers are incredibly complicated VMs. I would actually argue that my text-heavy content should be accessible via curl, like my other[4] projects[5]. I&#x27;ve never tried making a site browseable with curl before. That might be a fun experiment.<p>EDIT2: &lt;noscript&gt; should be working now, with a link to the raw content on GitHub, per danShumway&#x27;s suggestion (thanks Dan!).<p>[0] <a href="https:&#x2F;&#x2F;github.com&#x2F;anderspitman&#x2F;assg" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;anderspitman&#x2F;assg</a><p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;anderspitman&#x2F;anderspitman.net" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;anderspitman&#x2F;anderspitman.net</a><p>[2] <a href="https:&#x2F;&#x2F;anderspitman.net&#x2F;11&#x2F;dependencies&#x2F;" rel="nofollow">https:&#x2F;&#x2F;anderspitman.net&#x2F;11&#x2F;dependencies&#x2F;</a><p>[3] <a href="https:&#x2F;&#x2F;anderspitman.net&#x2F;13&#x2F;64-ms&#x2F;" rel="nofollow">https:&#x2F;&#x2F;anderspitman.net&#x2F;13&#x2F;64-ms&#x2F;</a><p>[4] <a href="https:&#x2F;&#x2F;patchbay.pub&#x2F;" rel="nofollow">https:&#x2F;&#x2F;patchbay.pub&#x2F;</a><p>[5] <a href="https:&#x2F;&#x2F;emauth.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;emauth.io&#x2F;</a>