☰ Menu

This article is an automatic translation of an article originally written in Spanish. View original article

Welcome to my Blog

One of my New Year's resolutions for 2026 was "share more." In all areas.

I've been making things for years that stay on my machine or in private repositories. Projects I start out of curiosity, tools I write because I need them, solutions to problems that probably someone else has too. And all that stays there, accumulating digital dust.

This blog is my attempt to change that.

The idea is simple: document what I do, share what I build, and in the process force myself to finish things. Because nothing obliges you to polish a project like knowing someone else will see it. In fact, the restlessness was already there last year when I decided to do something about my dissatisfaction with React and made PicoJSX. And, in fact, this site is proudly made with PicoJSX.

pico-xbar

To not stay just with intentions, I just published a tool that's become indispensable to me: pico-xbar

It's a lightweight fork of xbar, the macOS app that lets you display the output of any script in the menu bar. I've been using it for years, but it always bothered me that it consumed so much memory for something that basically has no graphical interface. It turns out that xbar loads a full WebView in memory even if you never open the plugin browser.

So I did what any reasonable person would do: I forked the project, removed Wails and the Svelte frontend, and replaced it with a native implementation using NSStatusBar via CGO. The result is an app that does exactly the same thing but uses ~20MB instead of 120MB+, and with fewer processes running.

It wasn't trivial, as xbar was built on top of Wails and I had to replace several very important things, but for the result and what I learned, it was worth it. In fact, just yesterday when I made the first release, it was the first time I automated signing and notarizing a .app package for macOS.

Pico-xbar has also been the perfect excuse to use Go in a full project. I started getting interested in Go in 2022, when I was considering a job change in my job search, but I set it aside when I started working at Rocketgenius (Gravity) at the end of 2022.

What's coming

I have several topics I'd like to write about in the coming weeks (months?), and also some private repositories that I'll clean up and publish as they become presentable: a somewhat more ambitious and chaotic Go project and a couple of smaller tools I've been making with Rust.

See you around.