Dear Iceland

Dear Iceland, this is not only a love letter, but also a letter which should give you moments of thought. I love you. Your nature is most beautiful, most astonishing, most cruel and also soft nature I have ever seen and I will likely ever see in my life. Your rivers, mountains, waterfalls and highlands are incredible. Your harsh winds keep one cold and shivering even if the sun burns. The sky looks more blue than anywhere in the world and the waters look more clean than air itself.

Three Spanish Boys in Iceland

This was written on 9th August, during my trip through Iceland. On this day we witnessed an accident of three young guys from Spain. They wanted to cross a river with their car, but got stuck and the car broke down. The complete car was in the river and drowned up to the steering wheel. After we pulled them out with our car (which thankfully has the right tools to pull 9 tons of weight) we noticed that the engine was broken.

Planning a log-functionality refactoring for imag

Here I want to describe how I plan to refactor the logging back end implementation for imag. This post was published on as well as on my personal blog. What we have Right now, the logging implementation is ridiculously simple. What we do is: On every call to one of the logging macros, the log crate gives us an object with a few informations (line number, file, log message,…) - we apply our format, some color and write it to stderr.

The pain releasing a multi-crate project

Today I released version 0.3.0 of my imag project, which contains over 30 sub-crates in the project repository. This was pain in the ass (compared to how awesome the rust tooling is normally). Here I’ll explain why, hopefully triggering someone to make this whole process more enjoyable. There is no cargo publish –all Yep, you’ve read that right. I had to manually cargo publish each crate individually. This is even worse as it sounds!


I will fly to iceland tomorrow. I’m really excited about this and I really hope I will have the opportunity to take great pictures while there. But vacation also means no activity on my open source projects. This post is mainly for your notice that there won’t be any updates on imag or other projects in the next weeks, until I’m back. I guess I have to set a photo gallery up when I’m back, so I can share the pictures I take in iceland.

A scale for describing the maturity of Open Source Projects

A major problem with open source projects is, that, most of the time, it is not clearly visible in which state the project is. At least not for a casual user of the software, for example a guy like me wanting to try the software. A version number can be a way to express a certain stability, especially if the project uses semver, though even a 1.0 in semver does not express the state a project is in, only that you won’t see breaking changes between (minor) version upgrades. - The new website

The website just got a new face. I was really eager to do this becaues the old style was… not that optimal (I’m not a web dev, let alone a web designer). Because the site is now generated using hugo, I also copied the “What’s coming up in imag” blog posts over there (I keeping the old ones in this blog for not breaking any links). New articles will be published on the imag-pim.

Why we need tools like git-dit

Right now, github shows you this: And these things will happen more frequently in future, I assure you! In the first half of 2017, we already had 3 major service outages, 3 minor service outages and 21 other problems. Yes, indeed, this is very good service quality. It really is. Anyways, it is not optimal. Github advertises itself with 22M developers, 59M repositories and 117k businesses world-wide, which is a freakin’ lot.

What's coming up in imag (25)

This is the 25th iteration on what happened in the last four weeks in the imag project, the text based personal information management suite for the commandline. imag is a personal information management suite for the commandline. Its target audience are commandline- and power-users. It does not reimplement personal information management (PIM) aspects, but re-uses existing tools and standards to be an addition to an existing workflow, so one does not have to learn a new tool before beeing productive again.

Use the overlay, Luke!

When working with Rust on NixOS, one always had the problem that the stable compiler was updated very sparsely. One time I had to wait six weeks after the rustc release until I finally got the compiler update for NixOS. This is kind of annoying, especially because rustc is a fast-moving target and each new compiler release brings more awesomeness included. As an enthusiastic Rust programmer, I really want to be able to use the latest stable compiler all the time.