After over 70 hours of gameplay spread across three months, I finally finished the Blue Lions route in Fire Emblem: Three Houses last Saturday. This was my third attempt at playing this game.
I had to quit playing the first two times because the hundreds of options the game offers for customizing character builds made me feel overwhelmed and anxious. Modern JRPGs have become surprisingly complex, although most of them last 60-100 hours (or more) so I suppose they give you plenty of time to get used to all the complexity.
Towards the end of Three Houses I discovered that it supports same-sex marriage. I wasn’t expecting this from a Japanese developer, least of all Nintendo, so it was quite a pleasant surprise!
In a few months I want to go back and finish the remaining three routes the game offers, but for now I’m taking a break from all the political turmoil and gray morality of Fodlan to play something on my other consoles.
Over the weekend I started a playthrough of Golden Sun on the GBA. After months of thinking about the best combination of stats for a large cast of characters, it feels good to go back to a simpler era.
I’m not a Rust expert by any means, but I’ve spent enough time with the language that I can write reasonable code with a bit of effort (and a lot of DuckDuckGo). However, I’ve found that I often hesitate to use it for my personal projects.
Rust is a large language. The sheer number of features and their complexity introduce so much cognitive overhead while writing code that I can’t always muster up the mental energy to use it for things I’m simply tinkering around with after work. It’s just not possible for me to keep the whole thing in my head.
If I was writing Rust for my day job, it would be a different matter. Using it to build production software every day would let me internalize it to the point that it would become mostly automatic. It would let me cement difficult concepts in my brain so that I wouldn’t have to go looking for explanations every five minutes (lifetimes, anyone?)
Sadly I only get to use Rust for one-off side-projects, which means I spend maybe two hours a week using it. This gives me barely enough time to get my code into a working state, let alone dive into things like the Rustonomicon or even macros.
I love Rust, so I’m going to continue using it despite my issues with it. I’ll just have to lower my expectations of the level of proficiency I can hope to attain with the language.
PS: somebody please give me a Rust job 😭
Much like how some people enjoy tinkering with motorcycles, electronics, or craft projects, I enjoy tinkering with software. If my computing environment stays the same for too long, I start getting restless. I crave constant change.
Emacs is a tinkerer’s dream, an infinite sandbox that can be molded into something entirely different each day. I can dive into the manual and discover new features, try different combinations of packages to see what’s most comfortable for me, glue together packages to make them do things they was never intended to do, write snippets of ELisp that help me get my work done faster, and so much more.
In this way Emacs is not only a tool that lets me do my job, but also a creative outlet that provides endless hours of entertainment and joy. I consider it one of the best pieces of software ever written.
Of course, there are other reasons for using Emacs — longevity, efficiency, ubiquity — but these features can be found in many other tools both free and commercial. Only Emacs is good at being Emacs.