Hello, world! My name is Jon Sangster (résumé) and welcome to my personal blog. This website is where I write about software development and Linux tips n’ tricks.
This entire site is literally generated from my notes, so don’t expect a well-polished experience. I plan for it to be less “medium.com influencer” and more “my first Geocities homepage.”
2. Recent Updates
Implicit conversion doesn’t come up very often in ruby. It’s a duck-typed language, so as long as an object has the right instance methods defined, everything should be fine. Sometimes though, when you’re dealing with system libraries or linking with other languages, ruby really does need a way to convert your objects into fundamental types, like strings, hashes, and arrays.
Most everyone I talk to about computers and software want things that “Just work!” The older I get, the more sympathetic I am to this view. There just isn’t enough time in the day to be futzing around with broken things; however, when it comes to my personal computers, I tend to run in the opposite direction. I just love to tinker, and my PCs provide the perfect playground for that. Whenever I find that they “Just work,” why, that’s perfect time to break them with some new project! As a consequence, these days I find myself running the unstable branch of NixOS.
One of the neat things about running on the unstable branch of an new-ish distro is that I often get to see bugs pop up before too many other people. When I used to run a very popular distro, like Arch Linux, solving a bug was mostly a matter of tracking down the forum post containing its fix. With so many nerds on the case, all the fun bugs are fixed before I’ve even finished my work day. With NixOS, if your system configuration is… unique enough, you could easily bump into a bug a day or two before anyone else does.
Earlier this week I ran into such a bug. When doing a system upgrade, I encountered an error for a package that I’m somewhat familiar with, and the error looked pretty easy, so why not take a shot at fixing it?
Hello, world! Welcome to my new blog. I plan to use this blog to document technical tips, hacks, bugs, coding “best practises,” and the like. Like many programmers, I spend heaps of my day, not implementing features, but trying to get a constellation of libraries, services, tools, and code to play nicely together. Normally, once I fix something, I immediately get back to whatever I’m supposed to be doing; however, I think it would be much more interesting to collect these in a blog!
Every Nix flake implicitly gets nixpkgs as an input, but what if it contains a show-stopping bug? It may have been fixed upstream, but these fixes can sometimes take days or weeks to even reach the nixos-unstable branch.
In this article, we’ll describe way one easy way to create a nix.flake that patches nixpkgs.
The goal of this page is to explore and document “best practises” for writing shell scripts and packaging them for the Nix package manager.
- This article describes software which is both: unstable, and something I’m still learning about. As a consequence, this advice may change over time.
I played Red Dead Redemption 1 on the PS3, back in 2011, and absolutely loved it. Well, Red Dead Redemption 2 (RDR2) was released a few years ago now, but this time I decided to wait for its PC release. I never did wind up buying a PS4 and rumours online are that RDR2 runs pretty well on Linux, via Proton, so why not?