oogabooga.inc 🫡 $3.7vps club member ($h3lp)
2K posts

oogabooga.inc 🫡 $3.7vps club member ($h3lp)
@myfknlimit
bad at comms, good at heart, ex-swe chap, now sadak-chap dabbling w local first tools and p2p systems








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.



The Japanese take their digital twins very seriously. Some amazing LiDAR and CityGML 3D datasets released by them too.


RLS was a mistake and folks exposing that level of complexity to less technical users is asking for trouble. It was a mistake in Firebase. It’s a mistake in Supabase. It will be a mistake in the next product too. I personally - even knowing how to secure it - would never touch it. It’s the worst security footgun you can imagine. One small mistake and your data is available to the world.












