uaksom

7 ms·

1.
by uaksom 4d ago
You're missing the point: LLMs are dangerous in the wrong hands, i.e., the frontier labs. They have shown zero desire to act responsibly.
2.
by uaksom 2mo ago
Changing core features every few months doesn't seem very consistent...
3.
by uaksom 2mo ago
It does seem like they're trying to convince themselves. If you like Zig, that's a good enough reason to use it. Why waste time on language tribalism? I have the same issue with "use the right tool" rhetoric. The right t
4.
by uaksom 2mo ago
> I invite you to read the release notes and see for yourself the types of breaking changes we’re talking about. I did, and I immediately found this in the latest release: https://ziglang.org/download/0.16.0/rel
5.
by uaksom 3mo ago
Earendil did! https://lucumr.pocoo.org/2026/5/24/pi-oss/
6.
by uaksom 9mo ago
(author here) If you run the parser under a debugger like lldb, then attempt to inspect the AST of a program, it appears as an array of u64. Not very useful, unless you work on special support for debuggers (such as a python script to unpac
7.
by uaksom 9mo ago
(author here) I agree that it's a lot of complexity, and I acknowledge this in the article: You can get quite far with just a bump allocator. I didn't go into this at all, but the main benefit of this design is how well it interac
8.
by uaksom 10mo ago
Using data races: https://www.ralfj.de/blog/2025/07/24/memory-safety.html
9.
by uaksom 2y ago
Thanks for the shoutout! We did recently add an export for LLMs[1], but weren't quite confident in how the big models handled it. The biggest issue we kept running into was that it would prefer using older APIs over the latest ones. I
10.
Zig; what I think after months of using it(strongly-typed-thoughts.net)
197 points by uaksom 2y ago|175 comments
11.
by uaksom 4y ago
They don't, at least not yet. https://github.com/lunatic-solutions/lunatic/issues/150 It is WebAssembly based though, so it should be easier than trying to deal with dynamic libraries and Rust's ABI
12.
by uaksom 4y ago
GC gives you a nice cushion, because it makes allocations fast. However, with a little bit of thought put into memory allocation (such as using arenas with bump allocation), you'd easily beat Go with Rust. The author of SWC did exactly