<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/feed.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://lars-christian.com/</id>
  <title>Lars-Christian's website - Notes</title>
  <updated>2026-04-20T20:30:06.563938+00:00</updated>
  <link href="https://lars-christian.com/" rel="alternate"/>
  <link href="https://lars-christian.com/notes/feed.xml" rel="self"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Recent notes</subtitle>
  <entry>
    <id>https://lars-christian.com/notes/2026-03-25-the-rise-of-markdown/</id>
    <title>The rise of Markdown</title>
    <updated>2026-03-25T00:00:09+00:00</updated>
    <author>
      <name>Lars-Christian Simonsen</name>
    </author>
    <content type="html">&lt;p&gt;Mat Duggan in &lt;a href="https://matduggan.com/markdown-ate-the-world/"&gt;Markdown Ate The World&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Markdown doesn't do most of what those formats do. You can't set margins. You can't do columns. You can't embed a pivot table or track changes or add a watermark that says DRAFT across every page in 45-degree gray Calibri. Markdown doesn't even have a native way to change the font color.    &lt;/p&gt;
&lt;p&gt;And none of that mattered, because it turns out most writing isn't about any of those things. Most writing is about getting words down in a structure that makes sense, and then getting those words in front of other people. Markdown does that with less friction than anything else ever created. You can learn it in ten minutes, write it in any text editor on any device, read the source file without rendering it, diff it in version control, and convert it to virtually any output format.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Informative and well-written post from Mat on Markdown's rise to prominence over the past few years. Lots of fascinating information in the backstory detailing the &lt;code&gt;.doc&lt;/code&gt; and &lt;code&gt;.docx&lt;/code&gt; formats about which I knew next to nothing. I just realised a few years ago that plain text was the way to go, and Markdown was the obvious choice at that point. Now I know more about why that was the case.&lt;/p&gt;</content>
    <link href="https://lars-christian.com/notes/2026-03-25-the-rise-of-markdown/"/>
    <published>2026-03-25T00:00:09+00:00</published>
  </entry>
  <entry>
    <id>https://lars-christian.com/notes/2026-03-29-old-os-x-versions/</id>
    <title>Old OS X versions</title>
    <updated>2026-03-29T00:00:08+00:00</updated>
    <author>
      <name>Lars-Christian Simonsen</name>
    </author>
    <content type="html">&lt;p&gt;Andreas in &lt;a href="https://82mhz.net/posts/2026/03/emulating-old-os-x-versions-with-qemu/"&gt;Emulating old OS X versions with QEMU&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;It's weird, because I never used these systems back when they were new, and yet I feel somehow nostalgic for them. I don't know why, but there's just something about the look of them. The colour palette, the skeuomorphism, the fonts and the overall design are just beautiful, and I wouldn't mind using an OS with this kind of look and feel today.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The early versions of Mac OS X were unequivocally better designed and a preferable user experience than the bastardised offspring that today's MacOS has become. My experience started with Tiger (10.4) and I would love to go back. In fact, if someone put together a Linux distro that closely emulates the early OS X aesthetic and UX, I would finally be forced to switch.&lt;/p&gt;
&lt;p&gt;If you want to experience the old OS X versions yourself, Andreas' post guides you through the process.&lt;/p&gt;</content>
    <link href="https://lars-christian.com/notes/2026-03-29-old-os-x-versions/"/>
    <published>2026-03-29T00:00:08+00:00</published>
  </entry>
  <entry>
    <id>https://lars-christian.com/notes/2026-03-30-small-workout-log-update/</id>
    <title>Small workout log update</title>
    <updated>2026-03-30T00:00:07+00:00</updated>
    <author>
      <name>Lars-Christian Simonsen</name>
    </author>
    <content type="html">&lt;p&gt;Well, I guess it wasn't feature complete after all. Easy to forget when you're mostly running on the treadmill. Once the hills come around, though, you know you need to log and display elevation gain, or climbing.&lt;/p&gt;
&lt;p&gt;So now my workout log does that. &lt;/p&gt;
&lt;p&gt;You can see this in the summary section of &lt;a href="/logs/workouts/2026/#300326Run5746-summary"&gt;today's run&lt;/a&gt;. As you can see, I climbed 140 metres. If you want to know the actual elevation profile, you can click on the &lt;a href="/logs/workouts/2026/#300326Run5746-elevation"&gt;elevation&lt;/a&gt; tab. This is just a little extra data point to give context to that visualisation. &lt;/p&gt;
&lt;p&gt;For new readers, if you want to know more about how I went about putting the workout log together, I've covered the process extensively in these three posts:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href="/posts/2025-07-20-my-blog-workout-log/"&gt;My blog workout log&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="/posts/2025-10-04-workout-log-and-site-updates/"&gt;Workout log and site updates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="/posts/2025-12-28-workout-log-now-totally-100-feature-complete/"&gt;Workout log now totally, 100% feature complete&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;</content>
    <link href="https://lars-christian.com/notes/2026-03-30-small-workout-log-update/"/>
    <published>2026-03-30T00:00:07+00:00</published>
  </entry>
  <entry>
    <id>https://lars-christian.com/notes/2026-03-31-software-used-to-be-better-designed/</id>
    <title>Software used to be better designed</title>
    <updated>2026-03-31T00:00:06+00:00</updated>
    <author>
      <name>Lars-Christian Simonsen</name>
    </author>
    <content type="html">&lt;p&gt;Rakhim in &lt;a href="https://rakhim.exotext.com/related-ui-elements-should-not-appear-unrelated"&gt;Related UI elements should not appear unrelated&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;A few years ago a new trend in UI design emerged where related elements would appear more and more detached and unrelated to the things they are meant to point to. &lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Somewhat related to &lt;a href="/notes/2026-03-29-old-os-x-versions/"&gt;my comments&lt;/a&gt; on old versions of OS X being much better designed that the current iteration, is this post where Rakhim points out that this goes for browsers as well. Nobody can claim with a straight face that this evolution isn't degrading the design and user experience.&lt;/p&gt;</content>
    <link href="https://lars-christian.com/notes/2026-03-31-software-used-to-be-better-designed/"/>
    <published>2026-03-31T00:00:06+00:00</published>
  </entry>
  <entry>
    <id>https://lars-christian.com/notes/2026-04-01-does-apple-even-have-a-vision-for-macos/</id>
    <title>Does Apple even have a vision for MacOS?</title>
    <updated>2026-04-01T00:00:05+00:00</updated>
    <author>
      <name>Lars-Christian Simonsen</name>
    </author>
    <content type="html">&lt;p&gt;Mat Duggan in &lt;a href="https://matduggan.com/i-cant-see-apples-vision/"&gt;I Can't See Apple's Vision&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The first time I thought "oh man, they've lost the thread" was Notifications. On iOS, Notifications make sense — you've got apps buried in folders three screens deep, so a unified system for surfacing what's happening is genuinely useful. On macOS, this design makes absolutely no sense at all.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I absolutely cannot wrap my head around notifications on the Mac. Why are they there? Where do they come from? Who decides what goes there? Every time I accidentally open that right sidebar, I'm always surprised to see a heap of notifications there. Should I be checking up on these more often? Am I missing out on important stuff?&lt;/p&gt;
&lt;p&gt;The concept of ‘notifications’ in a desktop environment simply doesn't make sense to my, admittedly not very smart, brain.&lt;/p&gt;
&lt;p&gt;Mat's post is spot on. Recommended reading!&lt;/p&gt;</content>
    <link href="https://lars-christian.com/notes/2026-04-01-does-apple-even-have-a-vision-for-macos/"/>
    <published>2026-04-01T00:00:05+00:00</published>
  </entry>
  <entry>
    <id>https://lars-christian.com/notes/2026-04-04-python-html-calendar/</id>
    <title>Python HTML calendar</title>
    <updated>2026-04-04T00:00:04+00:00</updated>
    <author>
      <name>Lars-Christian Simonsen</name>
    </author>
    <content type="html">&lt;p&gt;Alex Chan in &lt;a href="https://alexwlchan.net/2026/bin-calendar/"&gt;Creating a personalised bin calendar&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I start by generating an HTML calendar using Python. There’s a built-in calendar module, which lets you output calendars in different formats. It doesn’t embed individual date information in the &lt;code&gt;&amp;lt;td&amp;gt;&lt;/code&gt; cells, so I customise the HTMLCalendar class to write the date as an id attribute.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Neat post from Alex. Can immediately think of a few places where this approach might be useful. Also wish I'd known that Python calendar module fifteen years ago when I spent a not insignificant amount of hours setting up a calendar grid in Photoshop by hand ^_^&lt;/p&gt;</content>
    <link href="https://lars-christian.com/notes/2026-04-04-python-html-calendar/"/>
    <published>2026-04-04T00:00:04+00:00</published>
  </entry>
  <entry>
    <id>https://lars-christian.com/notes/2026-04-11-france-is-bacon/</id>
    <title>France is bacon</title>
    <updated>2026-04-11T00:00:03+00:00</updated>
    <author>
      <name>Lars-Christian Simonsen</name>
    </author>
    <content type="html">&lt;p&gt;&lt;img alt="Screenshot of a comment from reddit where someone explains that they misunderstood the name &amp;quot;Francis Bacon&amp;quot; as &amp;quot;France (the country) is bacon&amp;quot; and it is quite funny" src="https://lars-christian.com/notes/2026-04-11-france-is-bacon//FranceIsBacon.png"&gt;&lt;/p&gt;
&lt;p&gt;The internet used to be great.&lt;/p&gt;</content>
    <link href="https://lars-christian.com/notes/2026-04-11-france-is-bacon/"/>
    <published>2026-04-11T00:00:03+00:00</published>
  </entry>
  <entry>
    <id>https://lars-christian.com/notes/2026-04-11-the-wisdom-we-grow/</id>
    <title>The wisdom we grow</title>
    <updated>2026-04-11T00:00:02+00:00</updated>
    <author>
      <name>Lars-Christian Simonsen</name>
    </author>
    <content type="html">&lt;p&gt;I was going through my old notes and clippings (why is a big post in the making) and I came across this quote by Joel Miller. I don't know who Joel Miller is, but this quote by him feels more relevant than ever in the age of AI:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Our investment in reading changes the book because the book has changed us. ... If books are merely a means of transferring information, then perhaps, yes, a book is a waste of time. If a summary of its thesis and key points could be presented in a brief article or Substack post, why not just save the hours and read the Substack post? All the more if the information is outdated or questionable for one reason or another. But that mistakes what a book is for. A book is a tool. It’s a machine for thinking. And “all machines,” as Thoreau once said, “have their friction.” The time it takes to engage with ideas—whether factual or fictional, emotional or intellectual, accurate or inaccurate, efficient or inefficient—might strike some as a drag. But the time given to working through those ideas, adopting and adapting, developing or discarding, changes our minds, changes us. It’s not about the wisdom we glean. It’s about what wisdom we grow.&lt;/p&gt;
&lt;/blockquote&gt;</content>
    <link href="https://lars-christian.com/notes/2026-04-11-the-wisdom-we-grow/"/>
    <published>2026-04-11T00:00:02+00:00</published>
  </entry>
  <entry>
    <id>https://lars-christian.com/notes/2026-04-13-re-rss-feeds/</id>
    <title>Re: RSS feeds</title>
    <updated>2026-04-13T00:00:01+00:00</updated>
    <author>
      <name>Lars-Christian Simonsen</name>
    </author>
    <content type="html">&lt;p&gt;I'm inside my feed reader and I click a link to a feed. What happens? The link opens in my browser and the feed file is downloaded.&lt;/p&gt;
&lt;p&gt;Downloaded! When I'm in my feed reader and click a link to an actual feed. Come on guys! We need to fix this. But, given that Google hates RSS and are already &lt;a href="https://www.jmduke.com/posts/styled-rss-feeds.html"&gt;taking additional steps&lt;/a&gt; to kill its usability, I'm not too optimistic.&lt;/p&gt;
&lt;p&gt;We should be bringing back &lt;code&gt;feed://&lt;/code&gt; URLs and work to make them ubiquitous. The open web needs it, or an equivalent, in the fight against the lock-in of the tech oligarchies. &lt;/p&gt;</content>
    <link href="https://lars-christian.com/notes/2026-04-13-re-rss-feeds/"/>
    <published>2026-04-13T00:00:01+00:00</published>
  </entry>
  <entry>
    <id>https://lars-christian.com/notes/2026-04-19-another-workout-logger/</id>
    <title>Another workout logger</title>
    <updated>2026-04-19T00:00:00+00:00</updated>
    <author>
      <name>Lars-Christian Simonsen</name>
    </author>
    <content type="html">&lt;p&gt;Rishabh in &lt;a href="https://sigmarootpi.com/posts/2026-04-17-old-newspaper-like-blog-design/"&gt;Old newspaper like blog design&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I also added another category of posts, i.e., &lt;a href="https://sigmarootpi.com/workout/"&gt;workout&lt;/a&gt;, whose design is copied from Lars‑Christian's website. Thanks to Lars for the guidance.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Stumbling across this in my feed reader put a huge smile on my face! Risabh's workout log looks great, and it's so cool to have provided a little inspiration for someone else to take control of their data and share workouts on their personal website.&lt;/p&gt;
&lt;p&gt;Another great implementation is by Zak, who created a &lt;a href="https://fit.zkbro.com/"&gt;dedicated site&lt;/a&gt; on a subdomain for his workouts.&lt;/p&gt;
&lt;p&gt;Of course, I encourage both to create dedicated feeds for the workouts. That way, I can truly recreate the good parts of Strava (with none of the many drawbacks) by building a ‘workouts’ folder in my feed reader to draw inspiration when people get the work done.&lt;/p&gt;
&lt;p&gt;Hopefully many people will join us in sharing their workouts on their own websites like this, and this is just the beginning of the workout log revolution!&lt;/p&gt;</content>
    <link href="https://lars-christian.com/notes/2026-04-19-another-workout-logger/"/>
    <published>2026-04-19T00:00:00+00:00</published>
  </entry>
</feed>
