←
Leo3,620 posts
Leo avatar

Leo

@leo

Building — Prev. VP Product @vercel

◷ Joined March 2012▧ 227 Photos and videos
Leo avatar
Leo@leo·22 Oct 2025

Safari is the fastest and most efficient browser, and most people anyways use Safari on iOS, so using Chrome as default on desktop implies not having any cloud sync between devices.

Leo avatar
Leo@leo·22 Oct 2025

Brother from another mother. I thought I was the only one doing that. Safari is simply the best "consumption" browser, while Chrome is the best "creation" browser.

shadcn@shadcn21 Oct 2025

Same here. Safari is default. Chrome for dev work.

Signal avatar
⟳ Leo retweeted
Signal@signalapp·3 Oct 2025

We are alarmed by reports that Germany is on the verge of a catastrophic about-face, reversing its longstanding and principled opposition to the EU’s Chat Control proposal which, if passed, could spell the end of the right to privacy in Europe. signal.org/blog/pdfs/germany…

Leo avatar
Leo@leo·7 Sep 2025

Suspense in React is a solution to a problem that should have never existed in the first place. It exists to avoid blocking the UI on slow data and data waterfalls, but it is, in my opinion, fundamentally anti dynamism, anti personalization, and anti performance. Because the effort required to craft a clean UI with it is much greater than if it wasn't involved. A proper skeleton requires meticulous planning of all the potential states that a UI could be in, and then have those be represented as good as possible by the skeleton. It is always an approximation, and the worse the approximation is, the worse the user experience is. Whereas, if your data is fast, the final UI is not constrained to what the skeleton looks like, which enables the best user experience (no loading states), maximum dynamism, and thereby also maximum personalization. Of course this doesn't immediately work for any app of any size, but there is a wide range of small to medium apps for which it, in my opinion, makes the most sense. I created blade.im to make it easy to quickly build apps that offer maximum dynamism, however, without any loading states whatsoever. No skeleton, no SPA spinner, no slow TTFB. Every page render is a single database transaction, even if your layouts and page contain many dozens of queries. If you perform a write, the whole UI is updated for you, in the same transaction that performs the write.

Leo avatar
Leo@leo·12 Aug 2025

Man, @rolldown_rs is absolutely incredible. Great API. Excellent performance. A joy to use. I just landed Rust-powered builds on Blade with @OxcProject parsing plus rolldown bundling and was able to remove ~300 LOC (and counting) compared to esbuild.

Leo avatar
Leo@leo·26 Jun 2025

The best loading state is *no* loading state. The best skeleton is *no* skeleton. The best suspense is *no* suspense. Don't make your users wait because of technical constraints. UX comes first. Your users deserve what they want *immediately*, not later.

Leo avatar
Leo@leo·26 Jun 2025

Blade just went from 140 to 240 stars over night! Thank youuu! 🫶 Excited to announce: 📦 New package name: `blade` 🚀 New init command: `npm create blade` 🦕 Deno and Node support (prev. only Bun) 🖥️ Windows and WSL support 📃 Automatic table of contents for MDX

Leo avatar
Leo@leo·19 Jun 2025

Thanks, @theo! Working hard not to disappoint you! 🫡

1:33
Leo avatar
Leo@leo·17 Jun 2025

Trimmed down Blade's JSX stream parser a lot to reduce its impact on the client bundles, which must be as minimal as possible. We'll add size stats to the upcoming site.

Post attachment
Leo avatar
Leo@leo·2 Jun 2025

Inspired by nuqs, @nurodev added `useQueryState` to Blade, which lets you easily store state in the URL, as if it is `useState`:

Post attachment