Peter's DevLog

Epaper screens come in many variants.

Most developers will agree that having automatic tests is a good thing.

The most distinct part of making an epaper laptop is obviously the screen.

Ever since I got my first ereader twelve years ago I’ve wanted an epaper laptop.

Error handling, a contentious and oft-discussed topic.

Recently I was met with an interesting problem when wrapping a C library in Nim.

Nim is a great candidate for server development, but if you want to run your own server and are new to the world of server management or Linux there can be a daunting amount of information to consume in order to do it right.

As we discovered in my last article, Nim will by default generate C code and then call on a C compiler to actually produce a binary.

This is a question which has been asked in various places over the years, and recently on the forum in multiple separate threads.

This is a question that has come up time and time again in the IRC channel, when talking to people in person, and in the comment section pretty much every time Nim has an article on Hackernews or one of the bigger programming subreddits.

In the previous article we got a small primer on various kinds of multi-tasking, in this article we'll have a look at possibly the simplest form of this.

This is a series of articles about a topic in the Nim ecosystem that has so far been written fairly little about.

In order to stifle my tab-hoarding habits I have recently set my Firefox install to not recover sessions when I restart the browser.

For NimConf2020, our first virtual Nim conference, I realised how poor my microphone setup was.

In the first part of this article series we looked at why we would potentially want to be able to run NimScript embedded into our Nim programs.

In the first part of this three part article series we looked at why we would want to embed NimScript into our Nim applications.

[youtube BdQkU_HepIg] Over the past couple of years I’ve been playing around with creating my own WM.

Recently I got made aware that a comment I made on HackerNews had been linked to in a ZDNet article, this made me realise I should probably feature in here as well.

One feature in Nim that it shares with several other languages, especially functional ones, is implicit return of values.

History, as you might know, is of course the GNU History Library.

One thing I've mentioned about metaprogramming in Nim, both in posts on this site and in talks, is that metaprogramming in Nim can enhance read- and maintainability.

This article is intended as a companion to the lightning talk I held at FOSDEM 2019.

I recently had a look at a functional language named Toccata which amongst other things does away with booleans.

In a post over on Reddit someone noted that Nim doesn't really have any article or tutorial about file reading.

Nim recently had a stand at FOSDEM 2018.

While perusing the Nim subreddit I stumbled across a post asking for an explanation of how types work in Nim, especially how Nim allocates different types on the heap and the stack.

This site has been down for a couple of days now.

A while ago I read John Novaks great rant on how hard and annoying it can be to do something as simple as extending a cross-platform application with the simplest of GUIs.

Recently I held a presentation on functional programming at the University of Tromsø.

A while back I got myself a second hand Surface Pro 1.

In a previous post I wrote about how this website was created and how the content was managed with CouchCMS.

Lately I've been toying with the idea of creating a window manager for Linux.

After having decided that I wanted to create this DevLog I had to decide how I wanted to create it.

Over the years I've been involved with various projects, either by myself or through work.