Hi, I'm Konstantinos.

I'm trying to revive my old Macintosh Plus, and I got stuck on a surprisingly old problem: getting .hqx and .sit files into Mini vMac in a form it can actually use.

Barista 1.1 is out. It's the first feature release since launch: a command palette, your own global shortcuts, popovers you can pull off the menu bar, and deeper Calendar, Weather, Email and News widgets.

Some games on my Apple silicon Mac mini went completely silent while others played sound just fine. The culprit turned out to be an audio driver that Microsoft Teams had installed.

In the last post I wrote about what Barista is and why I built it. This one is about the building part: three problems that took far longer to figure out than they should have, and what I learned from each.

Barista's weather widget uses WeatherKit, Apple's weather service. Adding it was supposed to be a small change: enable the service for the app, add one entitlement, call the API. Instead, the next development build refused to launch. No crash report, no error, nothing in the logs under the app's name. The process was simply killed the moment it started (exit code 137, a SIGKILL).

Ten days ago I shipped Barista. This is a short write-up of what it is, what problem it solves for me, and a few decisions I made along the way.

A lot of what I do on my Mac during a day is small: check when the next meeting starts, glance at the weather, convert a unit, paste something I copied an hour ago, see what just landed in my inbox, jot down a note. Each one takes a couple of seconds. But doing it usually means stepping away from what I'm working on: switching to another app, opening yet another window, or hiding everything to get to the widgets on the desktop. And then finding my way back to where I was.

#include <stdio.h>

int main(void) {
    printf("Hello, World!\nThis is the first post on the blog.\n");
    return 0;
}