-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 - --- title: "New Blog" date: 2026-11-18T00:00:00+00:00 draft: false category: project excerpt: "I grew impatient with JavaScript and here we are." - --- # I didn't want to write a manifesto but here we are This blog is now nearly a decade old. How did that happen? :aaah: It was long overdue a makeover, so I decided to be ambitious and cast aside my static site, generated with [Hugo](https://gohugo.io/), and instead roll my own Go-based dynamic blog engine. :developer: ## The Creative Juice I'm a firm believer that the web should be an interesting place where everyone has the creative freedom to "make their mark". The expressiveness of what web technology allows is almost unbounded, and you end up with many fascinating sites as a result. There are design philosophies on one end of the spectrum such as [brutalism](https://brutalist-web.design/) and [minimalism](https://endtimes.dev/why-your-website-should-be-under-14kb-in-size/). There are people who write a lot of information and provide heavily-featured sites such as [gwern](https://gwern.net). You have other favourites of mine such as [ling's cars](https://museum.lingscars.com) and [low tech magazine](https://solar.lowtechmagazine.com/). The joy of the web is the diversity of content and presentation. It's part of what makes it feel so beautiful and _alive_. We get there by being opinionated, strange, personal, sub-optimal... _human_. ### Secret Sauce Markdown, for all its virtues, is a bit of a straitjacket. It makes everyone's content look identical. It's very easy to write a post and then just throw it on bear blog, substack, or whatever your poison, and it will look like every other post on said medium. It's a safe choice, but it's a damn shame to stifle unique expression and individuality for safe, boring conformity. :shame: This page is my attempt at fighting back against a homogenised web. I still use markdown for the core content of my posts, but I have extended the markdown syntax to allow for my own custom components. I can do things like inline reactions :meowheartbongo:, place specially formatted links to repositories [repo:WillMatthews/primeimage] and much, much more[^1]. Just enough to make the content ~wave:more "me"~ and less "everybody else". [^1]: Such as sidenotes. ## When all you have is a hammer A major gripe I have with the current state of the web is that it's full of JavaScript. JavaScript has its place but it's often used in excess - it's the reason why so many websites are lethargic and a drain to interact with. I appreciate that this is a bit of an extreme stance, but I have made the decision to not use any JavaScript on this blog[^demo]. [^demo]: The one exception is a standalone demo page that lives alongside a post, like the live demo in [the dynamic QR codes post](/posts/dynamic-resizing-qr-codes/). You have to click through to it on purpose, and the blog itself never runs a line. The reason is that I care deeply about the experience of my readers, and I want to make sure that it's as fast and responsive as possible. Once you start using JavaScript you end up seeing every problem as one that can be solved with JavaScript. The first script is the thin end of the wedge, and before you know it, you have a bloated, slow website that is a nightmare to interact with. :thisisfine: By way of example, we can look at GitHub. GitHub used to be written in Ruby on Rails and was server-side rendered. :vibepartycat: Now, it's a React app. (A very broken React app) :norwegianblueparrot: It's not the only reason, but it's a contributor behind why GitHub is now an inconsistent, slow, and frustrating experience[^2]. [^2]: I'm regularly confronted by GitHub whinging that it "can't show me all the files in this pull request because there are too many" or that "I can't render this diff because it's too big", and I can't help but think that if GitHub was still server-side rendered, it would be able to show me all the files and diffs without any issues. I mean, it's 2026 for god's sake :rage1:, why are we going backwards when I was promised everything would keep getting faster? When you look at an obvious regression like this, and at the modern web's steady march towards ever-thicker clients, you have to ask ["Why is it so?"](https://www.youtube.com/watch?v=mkocaEcx26c). Well, much like the reason why the RBMK reactor's control rods were graphite-tipped, the reason is that [it's cheaper](https://youtu.be/jBwSuSuGhyk?si=-tuFb3CBoe1i2KF9&t=47). :elmo-fire: It's cheaper for companies to do less work on their own machines and instead offload it to the client, even if it results in a worse experience for the end user. This is a shame, but it's the reality of the world we live in[^3]. [^3]: Well, until we are at the point where WASM can manipulate the DOM and we can have fast, interactive websites without JavaScript. But that's a topic for another day. What's especially defeating is I can't do anything but sound like an old curmudgeon complaining about the good old days. :depressed-wojak: Well, there's one thing I can do, and that's =make this blog not do that at all=. :gigachad: ## Goldilocks and the dynamically generated website I wanted a dynamic blog, but not one so dynamic that it was slow and bloated. I love the idea of the server sending a slightly different page to each reader: one that knows your theme, how many people have read the post, or just rolls the dice. :galaxy-brain: So the engine is a single Go binary leaning heavily on `html/template`, with SQLite underneath for the bits that change. The trick is doing the expensive work once. Every post is parsed and rendered to HTML when the server loads it and then kept in memory, so a request only has to wrap that HTML in the page around it and fill in the few things that move, like the view count. Images and other files get a hash of their contents in their URL, so your browser can keep them forever and never has to ask again. I set myself a budget of 800µs to render any page, and of 14 kB on the wire, so that a page [arrives in one round trip](https://endtimes.dev/why-your-website-should-be-under-14kb-in-size/). At the time of writing the home page renders in about 0.6ms and weighs 6.5 kB compressed; most posts land around 0.6-0.8ms and 10 kB. The honest exception is my [SimSPAD post](/posts/simspad/), which is a monster: about 2ms and 44 kB. I've decided that's the post's fault, not the engine's. :lul: ## Custom Components Back to the secret sauce. Because I own the whole pipeline from markdown to HTML, adding a new component is an afternoon's work rather than a feature request into the void. Repositories get their own cards, small inline ones like [repo:WillMatthews/dyn-blog] or a large one when I want to make a point: [repo-large:WillMatthews/dyn-blog] There are callouts, for when I need to raise my voice: > [!TIP] > Hover over a link to another post or an outside site and you'll get a preview of where it goes. No JavaScript involved; the previews are fetched once when I write the post, not by your browser. > [!WARNING] > The theme picker in the header actually works. Harajuku is there if you want to melt your eyes. :myeyes: There are also ==highlights==, ~~strikethrough~~, footnotes that can hold code[^code], and the reactions you saw earlier. Research posts can embed one of my papers, and every post has a "Cite this" box with BibTeX, so the academic in me is satisfied. [^code]: Code in footnotes? Why not! ```go func main() { fmt.Println("Hello from a footnote!") } ``` ## Things a static site couldn't do Going dynamic opened a few doors I'd been eyeing for years: - - **Themes without JavaScript.** Pick one in the header and the server remembers it in a cookie. The default follows your system's light or dark setting with nothing but CSS. - - **Kudos.** There's a button at the bottom of every post. It's a plain HTML form; press it if you enjoyed something. It costs you nothing and it makes my day. :catblush: - - **Webmentions.** If you write about a post on your own site, send a [webmention](https://indieweb.org/Webmention) and I'll see it. It's how blogs used to talk to each other, and I'd like that back. - - **The small web.** The same posts are served over [Gemini, Gopher and Finger](/smallweb), for anyone who finds even plain HTML a bit much. ## Here we are So that's the manifesto I didn't want to write. None of this is groundbreaking, and that's rather the point: fast, personal websites were never a solved problem we forgot about, just one we stopped bothering with. If you've got a site of your own, make it weird. Make it yours. :party-will: And if it's fast too, all the better. -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEJtHIQX7gIiqRWdSs/RuAbpOsR8kFAmr92qMACgkQ/RuAbpOs R8kmlA/+JwTeO+fzBYwAcDD9k7XPaboFQPpLqIOWsG5oxIlwqamZU8GqFBTVtyom X3+34fXLGOyn4xqYWrAxrTg56xto71Rr/SVBhFArHxrofQIlsSlfmhqvX2SBLf55 iT1z+ETarTH1ZRQ2dlWxcfjB41DgEacV8kPl4CcbhkBBnmBokShbGJmCrsZxMgzz xHfQ2kJXVbrsezcTZa5gJ4IqAkGhnIdgA0yYw1gqy7UppveQBhkCpfMaBgVIDxAh G49p+dPRqDZ6Zekj4QjFhrM0qzsBSeQrgLjKSOle7fYJ8V5OWNhpVbJv/7Bm6iL+ 0LTYMMZuvYGffkXezltA2q5CzCPMcQk4Aesbmd3zpRsvUEWn1gVAvZKhethOrB4P L+ZaWblvnN3hyQ6oApdgD39qKckh+8o9n7tUdpmow/Mlk3keM/oBwmrfKiRwgwUE BqZOLlSmZWhW1Fs20J3AymYY/PxMx5zwZ73pWhsWQuk/x5fkTG1q0FJaxwK0QJvG paRvPxlICNp+Qbhs7h+MZaSHjoKnOSXwWwY89DGci4obstqavXv+SvndCym8SRuE dwYx7/SSVBKLKv5W+OxRNY5gGuGE4QlvqVy//rBp+72K6txba+Yy1GqC/oghf7GM wwkQXFRHIY0u+/G1w1UOb9KAx9Lpb69mc+TBwzk3w8Y3JREm6+U= =7qNq -----END PGP SIGNATURE-----