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…

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.

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.

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

We're working on a docs site for Blade at blade.im — seems like someone already found the link 👀

Blade can now be deployed to @cloudflare and @netlify with zero config, in addition to @vercel and containers! 🎉 Let me know if there are any other providers you'd like to see added. I think @deno_land and @awsamplify would make sense?

Watching @anselm_io demo @jazz_tools at @localfirstconf. Super exciting!

By forcing your app to be rendered client-side, you are neglecting all advantages of RSC. Your initial page load will be a blank screen, your client bundles will become unbearably large (increasing the time to interactive), and so on. Better to stick to the Next.js defaults, IMO.