zlacker

[parent] [thread] 3 comments
1. Uninen+(OP)[view] [source] 2025-12-02 18:36:06
I'd say Ghostty is a pretty big success story as well.
replies(1): >>Cieric+U1
2. Cieric+U1[view] [source] 2025-12-02 18:43:37
>>Uninen+(OP)
Let's not forget about TigerBeetle either. They weren't bought (as far as I'm aware), but they seem to have some pretty good backing from customers.
replies(1): >>sgt+GB3
◧◩
3. sgt+GB3[view] [source] [discussion] 2025-12-03 19:06:55
>>Cieric+U1
Are the benefits of Zig really that amazing compared to Rust that it's worth choosing Zig, which is not even at 1.0 and seems to be constantly changing? Also, Zig is not memory safe the same way.

That said, I can easily imagine that the developer experience is superior for Zig. More fun.

replies(1): >>Cieric+vz7
◧◩◪
4. Cieric+vz7[view] [source] [discussion] 2025-12-04 22:09:45
>>sgt+GB3
At this point I'm not sure I can give a satisfying answer, but zig was just fun to use from the beginning. It was just c, but with a bunch of special features like comptime, the lessened foot-gun-ness of zig was just a benefit since most of the conventions were just things I was doing in my head but not putting into the code (since there wasn't really a good way to do so without compromise). The other thing I liked was I could just immediately read and write it without much looking at the docs. Their standard library was a bit of a hurdle, but the fact that the whole thing existed on my disk and I could just pop it open and read the code really helped (I assume this is the same with Rust, but I have trouble reading rust without going to lookup syntax). So while I can't give good reasons for using it in a commercial setting, for personal projects it was just fun. Rust in comparison hasn't really been fun to try and pick up.

At this point however I don't really like the way zig is going. So I won't really advocate for zig at this point, but I can say when I first started using it, it was fun and I could just write code that worked.

[go to top]