amgh

Introducing: Model Based Testing in Zig, A Preview of the Quint-Connect port written in the amazing @ziglang Watch as we find an invariant violation in realtime with some visualizations and @quint_lang magic! All of this as just a step in `build.zig`

Prime example of what it means to understand something vs vibe code it

@kitlangton can the state transitions be animated as well??

tuinking machines

I 🩷 @zeddotdev

@Med1_Ai why do i need to save it before it goes viral tho

🚨 BREAKING: Claude can now run your entire social media strategy like a $500/hour social media manager. For free. Here are 7 prompts you should be using right now: Save this before it goes viral.

starting to add an AI tag to my git commits so that my future self or another reviewer can go back to a commit and review if it was an AI one or not... sometimes im lazy in my personal projects and i want to understand later a few things later but still care about quality

@debasishg Agreed. In many cases the choice is going to be boiled down to simplicity of lifetimes in a program and iteration speed. These minor differences will impact the tradeoff decisions made by orgs or individuals when choosing between rust and zig for their projects.

matklad talks about Zig's • spatial and temporal memory safety • capabilities as a "dependent-types lite" cluster • absence of HM-style type inference with unification to avoid most annotations in generic code and why that's enough for Zig • convenience of comptime Here's the lobst .er link: #c_b5dj5q" target="_blank" rel="nofollow noopener">lobste.rs/s/b57uhm/funct… some of my thoughts on spatial and temporal safety that Zig offers .. I guess Zig's spatial memory safety in ReleaseSafe (and Debug) builds comes through runtime bounds checks on slices, arrays, and pointer accesses where the compiler can't prove safety at compile time. This is a big step up from C, where such checks are absent by default and overflows are undefined behavior (often leading to security bugs). For temporal safety, Zig offers some protection but not comprehensive guarantees. Its debug allocator (used in Debug/ReleaseSafe) detects many use-after-free, double-free, and leak issues at runtime with poisoning (e.g., filling freed memory with 0xAA patterns) and stack traces. Features like defer for cleanup, explicit allocators, and optional types help avoid common errors. However, it lacks Rust-style compile-time ownership/borrow checking, so temporal bugs are still possible if you misuse pointers across lifetimes (the programmer is ultimately responsible).

@appfactory we all do

i 🧡Zig

@jorandirkgreef @pavan4820 DPT!!! I was also thinking about this a while back.. can we deterministically calculate performance given exact parameters like through put, i/o, type of NIC, etc.. can't wait for what you guys cook..!

To start, the more “all in” on TigerStyle you go, the easier DST gets: - static allocation (often skipped) - assertions (sometimes skipped) - explicit fault models (including gray failure) - narrow interfaces (with weak expectations) - zero dependencies But to really do DST your simulator needs to be “Protocol-Aware”. For example, Determinism, say in a hypervisor is powerful and important, but you really want the simulator not only to be deterministic but also to “understand” your world, your protocol, to be able to reach in and know how far it can push things, where the breaking limit is, even w.r.t. things like optimal erasure coding or strict serializability or minimizing the number of messages for a recovery path. Then you start to be able to do things like Deterministic Performance Testing (DPT) which is where we’re exploring now.

yeah, this has been my experience with turso's simulator too, it's awesome when it works but chasing false positives is annoying. i have no idea how folks at tigerbeetle managed to do it so well lol.

@pavan4820 quint is goated

Another crash found with quint fixed few hours ago. github.com/sqlite/sqlite/…

@zeddotdev wtf

This has existed since before the dinosaurs, but it is totally a hidden gem.

I want to start an engineering heavy blog in my free time. Need help in choosing the best tools for this? I have heard about Zola but need more options to make a choice. Im going to get a fly.io vm soon. all suggestions welcome!

Learned a little geometry today, ported @steveruizok 's perfect-arrows library to Zig. It only draws straight arrows currently but had fun. Had learned a little geometry in school and used to like it, with LLM's it was easier to start from basics and start porting!

@LewisCTech Yes, to speed up their compilation: x.com/bunjavascript/…

@curlykoder what is "all the bun's zig fork". Bug has forked zig?

all the bun's zig fork to me seems nice and all but my perspective here is a software wins long term when it has soul. today, only humans can do this.

@shauseth zerodha has lesser headcount iirc

nikhil kamath has successfully built the most overstaffed podcast in history

@zeddotdev yay!

Features landing in the next few weeks: - Bookmarks - Helix Jump - Code lens - Markdown Renderer - Gif support, GFM callouts ([!IMPORTANT], [!WARNING], etc) - `git: view commit` action to look up commits via ref

@debasishg @AntithesisHQ haven't read much about it but what does prop based testing help to achieve which DST and MBT don't?

Hegel, from @AntithesisHQ is a universal property-based testing protocol and family of open-source libraries (for Rust, Go, C++, TypeScript, and more) built on Hypothesis, designed to deliver Hypothesis-level generation, shrinking, and test quality across any programming language. Spent some quality weekend time bringing Hegel-driven property tests for the porcupine-rust linearizability checker. Here's the implementation - github.com/debasishg/porc… Why Hegel when I already have proptest-based property tests ? Well first, it's fun learning Hegel, myself being a big fan of Hypothesis .. also see image👇 And if you want more details, here's a detailed comparison with proptest .. github.com/debasishg/porc…

@BenjDicken i currently work on all my projects by hand. sometimes i write from my brain but mostly i use AI to guide me sort of like mentor mode, so it would suggest code or fixes and i would either see it and type everything or understand visually then type it. rekindled my old spark!

The urge to learn [zig, rust, go] by-hand right now is incredibly high. Not because I think it's a better way to build software in 2026 (it's not) but because it's SO MUCH FUN. Remember the feeling of learning your first language? Your second? Third? How the intuition about language features and design steadily developed and helped you become the engineer you are today? Speaking of which, need to choose a topic for next stream series...

@leostera hyped to give the code a read

damn, comptime wins again! yesterday i vibed a little multicore actor runtime with cooperative scheduling and io for zig. it gives you typed messages between actors, ergonomic spawning of actors via fns and structs, and it handles moving actors around the cores for you. i am, very much, comptime pilled

@zeddotdev how to use this?

... interesting.