Doug Tangren 🐑

I'm on a curiosity voyage and these keys are my paddles 👨‍💻

Every time I open the internet I regret it

It isn't unexpected that the focus of the Bun Rust rewrite is on the anti-Zig side more than anything, since the internet loves to hate. What is unexpected and unfortunate is that leadership within Bun hasn't tried to steer the conversation away from that at all. There are so many positive and interesting takeaways from this and I'm not really seeing any of them pushed as the primary message. A positive thing that hasn't been talked about at all is how far Bun came thanks to Zig. And even if you dump it now, its meaningful for how good Zig was to even build a product to this point and impact by any metric. I would've loved to see anyone in leadership say this. On the interesting side is how fungible programming languages are nowadays. Programming languages used to be LOCK IN, and they're increasingly not so. You think the Bun rewrite in Rust is good for Rust? Bun has shown they can be in probably any language they want in roughly a week or two. Rust is expendable. Its useful until its not then it can be thrown out. That's interesting! There's been a lot of talk about memory safety and no doubt Rust provides more guarantees than Zig. But I'd love to see a better analysis of why Bun in particular suffered so much rather than take the language-blame path. How could engineering as a practice been more rigorous to prevent this? What were the largest sources of crashes other programs should watch out for? How does Rust prevent them? How could Zig theoretically prevent them? That's interesting. I know the official blog post hasn't come out yet from Bun. But they're smart enough to know that that PR would stir up controversy the moment it opened, or they should've been. And plenty in the company have been tweeting and writing about it. Its somewhat telling to me in various dimensions what they chose to talk about first. I tend to think I'm pretty good at corporate PR/comms (especially when it comes to developer audiences) and I think appealing to the negative is never the right long term strategy; it does work to get short term eyes though.

happy to announce htmx 4.0.0-beta3: #400-beta3---2026-05-08" target="_blank" rel="nofollow noopener">github.com/bigskysoftware… ships with two new extensions: hx-live with coarse-grain DOM reactivity & hx-nonce for better inline-element security enjoy!

moving at the speed of thoughtlessness

Vim に sixel をレンダリングする仕組みを入れてるんだけど、だいぶ安定しつつあるので、そろそろ pull-req に持っていこうか悩んでる。ひとまず Vim script で RGB 画像を動的に生成して動く xeyes を作ってみた。

It's beginning to look a lot like Christmas

We need a federation of forges blog.tangled.org/federation/

@mitchellh tangled.org might be at the right place at the right time

Ghostty is leaving GitHub. I'm GitHub user 1299, joined Feb 2008. I've visited GitHub almost every single day for over 18 years. It's never been a question for me where I'd put my projects: always GitHub. I'm super sad to say this, but its time to go. mitchellh.com/writing/ghostt…

Nvim 0.13 gained vim.ui.img, a stdlib interface for displaying images. - useful for markdown files, directory browse, picker preview, ... - ~small interface + impl cost. mostly a protocol change. - placement will be handled by extmarks or floating windows. - no builtin codec, not going to vendor a jpeg library.

Where can one buy a #jujutsu tshirt because I’m on the market for one? jj-vcs.dev/latest/

@GergelyOrosz If you want to own your data tangled.org is a pretty nice at proto based alternative

Pull requests disappeared on GitHub for many (all?) users. This is just the latest outage on a platform where reliability has been beyond unacceptable the last few months. A fair question: at what point would customers move? How much pain is too much? And where do they move?

Go 1.27 では uuid パッケージが入る予定。 #golang github.com/golang/go/comm…

I'm writing Go again (for what, you'll see later...). `go doc` and `gopls` are like agent superpowers and its shocking how productive agents are out of the box at writing [good] Go code versus other languages I've used (including the JS ecosystem). Also, Go + Zig is a good mix. Go for the higher level and concurrent stuff and then no-libc Zig code plus the Zig compiler for zero dependency cross-compiled cgo with high-performance characteristics (minimize cgo boundary crosses). Chefs kiss. Its funny because a lot of the shitty ergonomics of Go CLIs like `go doc` and `gopls` (prev. stuff like `go oracle` or `guru`) are totally obviated by agents and not just that but in a twist of irony they're excellent for agents. Don't worry, its not Ghostty. Ghostty and libghostty will remain pure Zig; it's a fantastic fit and a perfect pairing. This is for something else. "Wait, I thought you said Go has no place anymore?" I was wrong, mostly because agents are so productive at Go. I won't bring in other languages in this discussion because I don't want to feed the crabs, so to speak. lol.

last call for big sky dev con talk proposals: docs.google.com/forms/d/e/1FAI… conf is july 24/25 here in bozeman, this year on campus at Montana State should be fun!

TIL you can enable vim motion based terminal navigation in any shell with with set -o vi

⚡️ Zig 0.16 is out. And the new I/O model is a huge shift. • Swap implementations (threaded, evented, etc.) • Write code that looks blocking but runs async • Composable like allocators #toc-IO-as-an-Interface" target="_blank" rel="nofollow noopener">ziglang.org/download/0.16.… #zig #ziglang

it is confirmed, we reached AGI

@viggy28 @anuraggoel @golang @render @Cloudflare For the right problem … when they hit 58M req/s. Sounds about the right time to start reaching for an optimization

@anuraggoel @golang @render Big fan of Go here too. But scale matters - Render's 150B/month ≈ 58K req/s. @Cloudflare rewrote their proxy in Rust (Pingora) when they hit ~58M req/s, roughly 100x that. blog.cloudflare.com/pingora-open-s… So, it's about picking the right tool for the right problem.

Our @golang load balancer at @render handles more than 150 billion HTTP requests a month across millions of services. The number of times we've wanted to rewrite it in Rust: zero. Go is the most underrated language in infrastructure. "Boring" is the ultimate feature.

AI code generation and review is very useful… when you are building something that already exists… in a state from how that would have been built 3 or so years ago