Duane Bester

Dog: is barking Kids: are crying Nanny: is nannying AirPods: Increase the volume for your Blink 182 song 🎵 Me: I FELL IN LOVE WITH THE GIRL AT THE ROCK SHOW Claude: **Prompt cache placement** — Good observation. The intro is only ~3

@realsigridjin For F1 fans: like Hamilton joining Ferrari

For my non-tech friends, this is like Messi joining Real Madrid

ora.ai/score/toolshed… Toolshed scored a “D” But it’s an http landing page describing an ssh server that’s made for agents so idk. Their tool just limits itself to http? Agents can use toolshed _really_ easily.

This is what actually impressive engineering looks like.

@iavins Probably not @TigerBeetleDB

👀

@poteto github.com/duanebester/go… 👀

let’s reinvent guis from first principles

@anthdm I’ve had a great time with zig and latest LLMs

I'm starting to think that Anthropic (that acquired Bun) is forcing a Rust rewrite, so their shitty engineering team can help messing it up by prompting Claude. Zig is nice but the training data is always outdated due to Zigs breaking changes every month. just my 2 cents

@jorandirkgreef @appfactory 💯

We’ve had on the order of 3 memory bugs in 6 years of TigerBeetle. None RCEs. On the other hand, our own simulators have proactively found hundreds of (devastatingly catastrophic) distributed systems correctness bugs per year. Given how hard TigerBeetle’s domain is, in terms of mission critical financial transaction processing, I’ve never for one minute believed that writing TB in a memory safe language such as say TypeScript would somehow magically (!) make any material impact compared to the 100x correctness multiplier of TigerStyle. That’s because—rather than fall for the fallacy of composition, i.e. to see distributed correctness as a language problem—TigerStyle instead takes ultimate responsibility for the “end to end” correctness of the distributed system as a whole. Per systems engineering, correctness is always a systems design problem. For example, how to build a reliable whole, (especially) out of unreliable parts, such as broken firmware, bitrot, programmer error etc. In other words, application of the end to end principle. But when you TigerStyle the design in this way, the world of systems engineering also completely opens up to you and changes how you evaluate systems languages (now things like “power to grammar ratio”, or explicitness, checked arithmetic and precision become more critical and valuable to you). Of course, it is harder to care about correctness, to take responsibility for correctness end to end. Yes, you’re forced to begin to worry about the more serious concerns, starting with the basics of static allocation, explicit limits, assertions, deterministic simulation testing and moving to more advanced topics like protocol-awareness and storage fault-tolerance. But then again, TigerStyle is such a force multiplier, that you achieve mission critical quality, and in less time and with greater velocity. If you’re tired of production issues, and if you want to “engineer your engineering”, I would encourage you to lift up your thinking to the level of systems design and end to end correctness. Start thinking about your methodology and begin embracing TigerStyle. tigerstyle.dev

Running a chat app at scale is like, a whole thing

@sineptic0 @saltyAom GPUI uses Box<dyn Trait> at runtime; Gooey checks backend signatures at comptime. cx.update(State.increment) vs cx.listener_for(view, |view, e, win, cx| ...). Zig infers the state type from the method pointer. No closure boilerplate.

@sineptic0 @saltyAom Partly Zig — no traits = no clean way to share setters across element types. Mostly policy: static alloc, hard limits, WASM stack budget. POD structs + comptime tuples beat heap-built fluent chains.

Mythos, migrate GPUI to Zig, make no mistake

@blelbach Playing with something similar, but macOS only and on a smaller scale. Still a ton of fun! github.com/duanebester/nn…

Zig is very much on my radar as GPU language these days. If someone wants to pitch me on this, send a DM.

@reillyjodonnell @saltyAom Thanks so much! Going through some hiccups with the Zig 0.16 migration. But it’s super fast, is decently feature complete, and has 1 small dependency that I’m thinking about bringing into the codebase

@duanebester @saltyAom This is great!

@huacnlee Making progress

And will be using gpui component! @huacnlee

Working on something fun - GPUI support for json-render! @ctatedev @zeddotdev

@sudobunni @dhh Really liking this idea 💡

Hey @dhh buying physical copies of omarchy installers with art boxes like this would be so sick

@the_gpc_ @jorgemchagas

Photographers, show us a picture YOU took. No description. Just a pic. 📸

@aestheticsguyy @Raylivez1

Post a picture YOU took. Just a pic. No description

Opus is so good at Go and Zig