←
clipperhouse21,492 posts
clipperhouse avatar

clipperhouse

@clipperhouse

Engineering & epistemology. Former Neon, Cockroach Labs, Stack Overflow.

◷ Joined March 2008▧ 1,014 Photos and videos
clipperhouse avatar
clipperhouse@clipperhouse·Nov 10

Sad to hear this. His style was a bit derivative of the Strokes though. Jokes aside, this solo is in my top 3, it’s a jackhammer: youtu.be/rjffOMJxXlY I think about bands being greater than the sum of their parts; Lloyd elevated Television from art installation to rock band.

Richard Lloyd has died at 75. The Television founding guitarist learned guitar with Jimi Hendrix’s protégé, helped make CBGB a legend and wove the dazzling interplay of ‘Marquee Moon’ with Tom Verlaine. zurl.co/C69Rr

clipperhouse avatar
clipperhouse@clipperhouse·Nov 3

Imagining that Omarchy 5 or 6 will be the OS the most modern dependency management (Nix) and the most modern window management (Rex).

Close, but wrong direction. Let’s build a new modern window server starting from terminal primitives so we can eventually build better GUIs. As a hint, the Rex server has zero knowledge about terminals :) they’re just an app.

clipperhouse avatar
clipperhouse@clipperhouse·Sep 8

Desktop agents + Omarchy = bad for services revenue for Mac & Windows.

1/ today we're rolling out Muse, our new personal ai assistant. Muse is always-on, wicked fast, can use a browser, connect to your apps, and is designed to be secure. try it now: muse.ai.

2:00
clipperhouse avatar
clipperhouse@clipperhouse·Aug 24

Seems to me one could simply run this locally on your machine. Your local config (and auth) is only S3. Don’t need a shared server.

Git at Scale (by cursor) has been one of the most interesting blog posts i've read in a while. It came right when I was frustrated with Shopify's internal git system. As an exercise, I've implemented it over the weekend as open source. It's a single rust binary that you can point at any S3 type object store. It uses WAL and CAS primitives and requires no other data store. It also implements bundle-uri so large git repos (like our mono) are very fast to download as a chain of static bundles. Also comes with basic familiar UX. github.com/tobi/walgit

Post attachment
clipperhouse avatar
clipperhouse@clipperhouse·Jul 3

God’s Comic, Green Shirt, Clubland, All This Useless Beauty, Taking My Life In Your Hands, No Action

My Top 10 Elvis Costello Songs! 1. Brilliant Mistake 2. Beyond Belief 3. Accidents Will Happen 4. Radio Silence 5. New Amsterdam 6. I Don't Want To Go To Chelsea 7. Tramp The Dirt Down 8. Little Palaces 9. Red Shoes 10. Strict Time + 13 Steps ... My Little Blue Window This Town

clipperhouse avatar
clipperhouse@clipperhouse·Jun 19

Clean electric guitars sound dirtier than other instruments. It’s a raspy thing in the best of circumstances.

What most don't realize about Paul and many of this generation are two things. 1. The amp is cleaner than it sounds. 2. Standard Tuning. Proving... You don't need maximum gain and a down tuned baritone to sound heavy in Rock. The riff is the star. 😎👍

4:32
clipperhouse avatar
clipperhouse@clipperhouse·Jun 12

If you know the story of the rock band Rush and have seen the YouTube videos from the tour this week, they will bring a tear to your eye. Anika Nilles is a hero.

clipperhouse avatar
clipperhouse@clipperhouse·May 3

Ever get one of these? Today’s Wordle. ⬛⬛⬛⬛⬛ ⬛⬛⬛⬛⬛ 🟩🟩🟩🟩🟩

clipperhouse avatar
clipperhouse@clipperhouse·Mar 24

Very true. Databases do a lot caching (from disk mostly) and keep it consistent, even when we aren’t paying attention. If at all possible, just use the database. Optimize the queries. Databases have also figured out the hard parts of replication: transactions and ordering. Hit a database secondary if you don’t wanna hit the primary. There is exactly one dimension of inconsistency, which is time. Third, use an analytics database if you want aggregation. Accept the time delay and design for it. Almost never, in my opinion, is “database data in Redis/memory” the right answer, unless you are very tolerant of inconsistency.

Cache invalidation is hard because the moment you copy data to make a system faster, you create two truths that can drift apart: - One is the real data, - one is the saved fast version. "Just update the cache when data changes" is practically useless advice. That only sounds clean if you ignore delays, failures, race conditions, multiple services, retries, out-of-order events, and users reading data while writes are still moving through the system. In general, you need rules for - when the fast version is still safe, - when it must be replaced, - who decides that, - what happens when that decision is late, lost, or wrong. Cache invalidation is a constant trade between speed and correctness, and people often pretend they can fully have both.