Cuando una aplicación necesita leer un archivo, escribir en una conexión TCP o esperar datos de un disco, el kernel de Linux ofrece tradicionalmente dos caminos: bloquear el proceso hasta que la operación termine, o usar interfaces como epoll y Linux AIO para manejar múltiples operaciones concurrentes. Durante casi tres décadas, esas fueron las opciones dominantes. Pero desde la versión 5.1 del ke
When Google announced the Manifest V3 deadline, the developer community had a lot to say — most of it negative. The service worker model was rightly criticized as a regression for ad blockers and complex extensions. I've now migrated 18 extensions from MV2 to MV3, or built them MV3-native from the start. The commonly documented issues (no persistent background pages, limited webRequest) are real.
Reading a long-form piece on, say, the Peloponnesian War. Thucydides gets mentioned as a primary source. I half-know who he is — historian, Athenian, that's about it — but not enough to understand why the author is citing him specifically over Herodotus. Opening a new tab means I lose the sentence I was in. Skipping it means I read shallower than the text deserves. rabbitholes is a Chrome extensio
Most "online ruler" pages look simple: draw a rectangle, add centimeter ticks, add inch ticks, done. That works only if every screen maps CSS pixels to real-world size in the same way. They do not. A 13-inch laptop, a 27-inch external monitor, a phone, a tablet, and a 4K display can all render the same CSS width with different physical sizes. Browser zoom, operating-system scaling, Retina-style di
Notes written in the field are good at recording results and reflections, but keeping the flow that led to those results as structure is surprisingly hard. The procedure that lived only in someone's head at the time, the implicit assumptions that didn't make it onto the page, the judgment calls that got summarized away in meeting decks — when you read the notes back years later, those rarely survi
TL;DR I try to keep my eyes on the AI agents. I gave one too much rope once, and the kind of mess it made while I wasn't watching is something I'd rather not retell. Which is why I needed 5 monitors. To run 5 agents in parallel, 5 VSCode windows have to live in one field of view. Physical monitors hit a wall. No desk fits five; even my viewing angle gives out before the desk does. So I strappe
I wanted to ask AI about it, but the flow was annoying: switch to a browser, open a chat tab, copy or type the error, wait for an answer, then switch back. After doing that too many times, I started building something that works directly on the desktop. That became Xerolas. Xerolas is an AI screen lens for your desktop. It works like this: Press Ctrl + Shift + Space Drag over any region of your
Lately, I’ve been reflecting on something: The question for most developers is no longer "Are you using AI?", but rather "How and why are you using AI?". I’ve noticed AI tooling becoming increasingly embedded in my daily workflow. At this time last year, my usage of AI was limited to code autocomplete suggestions in my IDE that I would manually validate. Now I am using coding assistants to help id