Things I use.
I don't care too much about hardware, so this is a rather short list.
In general, I prefer tools which are leightweight and fast and do one
thing well. If I have to choose between two tools for a job, I will opt
for the one which is more lightweight, has fewer dependencies, or which
(being an OpenBSD user, see below) is part of OpenBSD base.
- OpenBSD
-
After having used various Linux distributions for many years, I feel
like I have finally found my (close to) perfect operating system. It is
small, clean and simple, and perfectly suits my needs. It just
feels right.
While not all of the hardware inside the Medion AKOYA E4253 is
currently supported by OpenBSD (in particular, iwm(4) does not support the
Intel Wireless-AC 9462 internal WiFi adapter), it runs reasonably well
on it altogether. Here is my dmesg
(OpenBSD 6.9).
More information on OpenBSD can be found on my OpenBSD page.
- nvi
-
I was a Vim user for many years,
but recently Vim started to feel too bloated to me. Therefore, I
switched to nvi and never looked back since then. It turns out that
many features I once thought were indispensable are in fact very easy to
live without. For instance, read this
if you think you can't do without syntax highlighting (as I did), and this
if you think it is a drawback that (n)vi lacks all the features Vim has
to offer (read it even if you don't). The only thing I really miss is
Unicode support, which is why I have to revert to nvi-iconv instead of
being able to use the default version, vi(1), from OpenBSD base.
More information on the vi editor can be found on my vi
page.
- cwm
-
I have used many different window managers in the past, most recently xmonad, which I was quite fond of (not
the least because it is written in Haskell). cwm(1) is part of OpenBSD base,
and I didn't even know it before I switched to OpenBSD. Finally a
window manager which is simple, minimalistic, effective and unobtrusive.
- ksh
-
I spend a lot of time in the terminal, and OpenBSD's default shell ksh(1) delivers everything I
need. Part of OpenBSD base.
- tmux
-
Since I spend a lot of time in the terminal, a terminal multiplexer is a
must, and tmux(1) is the
obvious choice. Part of OpenBSD base.
- RainLoop
-
Ideally, I would only be using Mutt. Due to the proliferation of HTML
e-mails, however, this is simply not feasible any more. RainLoop is a
webmail client and the best alternative I know of, and really simple to
set up (see Installation and Setup of
the RainLoop Webmail Client on OpenBSD).
- MuPDF
-
A fast and lightweight viewer for PDF files with vi-like keybindigs.
- feh
-
A fast and lightweight image viewer.
- FFplay
-
I rarely need a media player, but if I do, I will use FFplay from the FFmpeg multimedia framework.
- sct
-
sct is a small tool which sets the color temperature of the screen.
This makes it possible to have warmer screen colors at night, when the
surroundings are dark. It is similar in functionality to f.lux and Redshift, but much smaller and with
much less dependencies. Created, somehow fittingly, by OpenBSD
developer Ted Unangst.
- Asciidoctor
-
Asciidoctor is a very fast text processor for the AsciiDoc markup
language written in Ruby. It has great documentation and can directly
generate PDF as output. I haven't used traditional text processors in a
long time, mainly for two reasons: First, there is no separation of form
and content whatsoever, which implies that content written in some text
processor is always bound inextricably to the text processor itself.
And second, they are much too complex and bloated for my taste, and in
almost every case employ a GUI. Having used LaTeX a lot during my studies
of physics – doubtless the best markup language and typesetting
system for mathematical documentation –, it was also my first
choice for creating other forms of documentation (like letters) for a
long time. LaTeX is not really lighweight though, and while it is
practically indispensible for creating mathematical and physical
documentation, it is overkill for my typical purposes these days.
Therefore, I have come to use AsciiDoc in most situations, which
involves little markup at all.