The Unicode standard allows for certain (visually) identical characters to be represented in different ways. For example the character ä may be represented as a single combined codepoint "Latin Small Letter A with Diaeresis" (U+00E4) or by the combination of "Latin Small Letter A" (U+0061) followed by "Combining Diaeresis" (U+0308). The semantic meaning and visual representation is exactly the same, but the codepoints are different. How do you deal with that?

After working through “the book” on the Rust programming language and getting started with the first non-trivial, real-world application I found myself faced with a question I didn’t yet feel well-equipped to handle: “How should you structure error handling in a mature rust application?”

A look at the new plugin package coming in Go 1.8 - a bit of background, a look on how to make use of it and some of its (current) limitations. Recent Go releases have introduced a number of different ways to compile Go code. With Go 1.5 for example…