The years-overdue announcement post for FlickBoard
(Or: How I fell into the (mobile) keyboard rabbit hole.)
(Or: How I fell into the (mobile) keyboard rabbit hole.)
In which I painstakingly remove functionality from a Linux live image. Like a normal person.
If you use Kubernetes on a regular basis, you've probably came across the dreaded context .
Back when I was a kid, there was a lot of talk about website defacement. Y'know, when someone would break into some high-profile site and replace it with some message about how "xXwhateverXx Waz Hear".
Every once in a while, we all feel the need to modify something that someone else built.
There's a lot of talk about UX (User Experience), and DX (Developer Experience). But those are usually focused around, well, active users. How does the experience for leaving look?
I always liked the concept of blog comments. I largely write for myself, but it feels strange to just see the void stare back at me.
At some point get around to writing a longer post about why I don't really like jj/jujutsu . But at least it turns out it's at least pretty easy to block it from my repositories.
So, we've covered polling . We've tackled sleeping (and waking ). Going back to the definition , that leaves us with one core concept left to conquer: pinning !
So. You've read my last post . You got inspired. Excited, even. Deployed SimpleFuture to production. Spun up a few worker threads to share the load. Called it a friday. This is Rust after all, what could go wrong? ...aaand then someone took a look at the CPU usage.
There are a lot of guides about how to use async Rust from a "user's perspective", but I think it's also worth understanding how it works, what those async blocks actually mean. Why you get all those weird pinning errors.
Well, I just picked up this game called Wanderstop . Or, well, picked it up a few days ago, but I just finally got around to finishing the prologue, stopped crying, and felt like I had to go write. Beware of spoilers for the tutorial below the fold. Wait, can tutorials have spoilers? Does that even make sense? Is calling it out as a spoiler a spoiler in itself? What about when the same things are…
No, you can't talk about that here, that's off topic. This is a site about programming.
I wrote this Android keyboard named FlickBoard . A few people even seem to like it, strange as that feels to say. Since the project is now a smidge over a year old I figured it'd be worth writing about how we got here, and where I'd like to go from here.
A few days ago, I was talking to an old friend of mine about that weird project I've been working on for the last few months .
I've been using Nushell for a while, but mostly as an interactive shell. The other day I ended up writing my first nontrivial script with it, and... oh boy. There's an Emacs mode , but.. it only covers syntax highlighting, not highlighting.
I love systems. The idea of them. Thousands of pieces, each doing a simple - almost trivial - task, but coming together to form a beautiful tapestry. Maybe you've seen Wintergatan's Marble Machine , or one of the many Lego Great Ball Contraption builds out there. It's almost mesmerizing to watch. Maybe it's what fueled my multiple addictions to OpenTTD and Sweet Transit 1 .…