Recent submissions

Comment · 3 days ago
Comment · 28 days ago
Comment · 3 months ago
Sure. My reference to BIBO borrows the idea from control theory that if you put bounds on your input, your output will likewise be bounded given your system is BIBO-stable. Applying this to software, if you constrain the range of input to values that will be correctly processed, then you could exploit this to write less code (example: relax building type-checking and error handling code if you know the input is going to be an integer). I’ll caveat that this is not guidance, but more observation, particularly for the case where the audience is one as opposed to many.
Comment · 3 months ago
Wasn't aware of org-sync until now. That said for my use case I still would not use it as I didn't want to setup another GH authentication token for another client. YMMV.
Comment · 3 months ago
Thanks for sharing this! You are a legend!
Comment · 3 months ago
Seeing how much functionality I could get from just 400 LoC was one of the motivations for writing this post.
Comment · 3 months ago
Short answer, yes I am a Mac guy. AFAIK, both AppleScript and Shortcuts/Intents are mechanisms Apple has provided to support orchestration between apps. I do not consider them “malleable computing” mechanisms as they do not allow for adapting and reshaping the apps themselves. That said, AppleScript and Shortcuts are only as useful as the support given to them by 3rd party apps, which IMHO has always been mid.
Comment · 3 months ago
NGL, whenever I work with Cocoa APIs, I wistfully think of another timeline where we get a system-level SmallTalk style REPL and ecosystem accessing all of it.
Comment · 3 months ago
OP here. Happy to answer any questions about my post in this thread.
Comment · 3 months ago
OP here. This post resonated far more than expected. Thanks all for the feedback!
Comment · 3 months ago
In retrospect, the name `emacsclient` was a poor one because in 2026 most folks new to Emacs expect it to act like a REST client, where runtime state is synchronized between the client and server over a network. Emacs' usage of ‘client’ and ‘server’ here refer to the usage of a Unix local domain (i.e. file system) socket for simple control commands from the socket client. This was later extended to support a network socket, but the client still only sends simple control commands.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton