I think Rust is officially comfy as a language for backend and/or web service development, but upcoming uncomfyness looms ever-present.

At work I’ve been working on a simple encrypted flash abstraction using AES-XTS on the block layer and littlefs as file system, which reading the blog post has some really nifty features when dealing with microcontrollers.

Since I haven’t blogged in years and I feel like starting again I thought it would be a good idea to start with something negative that always irked me, the state of build systems for C and C++.

Recently I’ve been playing WATCH_DOGS and I thought, I want to be a cool hacker too!

This is the tale of a gate, OpalGate to be precise, or at least that’s how it’s been dubbed by triggered purplehairs.

I recently decided to create my own browser, exactly fit to my needs, because the future of Firefox addons I strongly depend on is kind of uncertain.

I was playing with DETS and I kept getting weird { error, { bad_object_header, * } } without understanding what was going on.

My life is currently at its peak, the years of work have finally come to realize what I wanted to achieve.

From the previous post about stringifying things, comes inspect, it’s an improved version of stringify and actually returns inspecting strings like Ruby does, so it’s not for stringifying, you should use an internal standard for that and use the appropriate methods and functions.