Earlier quoted context omitted.
Ghostty https://ghostty.org
Another one to the list, however it hardly sounds like a killer application.
Zig – io_uring and Grand Central Dispatch std.Io implementations landed
71–80 of 315 posts
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#72I feel like it's worthless to keep up with Zig until they reach 1.0. That thing, right here, is probably going to be rewritten 5 times and what not. If you are actively using Zig (for some reasons?), I guess it's a great news, but for the Grand Majority of the devs in here, it's like an announcement that it's raining in Kuldîga... So m'yeah. I was following Zig for a while, but I just don't think I am going to see a…
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#73Earlier quoted context omitted.
Remember that it was Jai that inspired all these new languages. When you talk about the capabilities like comptime, that's all from Jai and why John no longer does public presentations(as people keep stealing his unfinished ideas). Your comment about gamedev focus makes no sense as that it the most hardcore segment of all the programming there is. So if a language is good for gamedev, it's good for everything else -…
> Remember that it was Jai that inspired all these new languages. Not really. Rust was a thing long before Jai.
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#74Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#75I’m waiting for the kqueue implementation.
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#76Earlier quoted context omitted.
I’m a casual user and the 0.16 changes scare me. I tried multiple attempts now, even with full LLM support to upgrade and the result is just a) painful and b) not very good. I have high doubts that the current IO system of 0.16 will make it for another release given the consequences of their choices.
Here's some advice: 1. if you're a casual user (ie you don't follow the development) don't try incomplete APIs that not even the creators of fully know how they are supposed to work (because they're still tinkering with them) also you can't expect docs until the design is somewhat finalized (which is not yet, fyi) 2. llms don't help when trying to make sense of the above (a feature that is not complete, that has no d…
Is the completeness of each API formally documented anywhere? Maybe I missed something but it doesn't seem like it is, in which case the only way to know would be to follow what's happening behind the scenes.
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#77I feel like it's worthless to keep up with Zig until they reach 1.0. That thing, right here, is probably going to be rewritten 5 times and what not. If you are actively using Zig (for some reasons?), I guess it's a great news, but for the Grand Majority of the devs in here, it's like an announcement that it's raining in Kuldîga... So m'yeah. I was following Zig for a while, but I just don't think I am going to see a…
For what it's worth, Bun is written in Zig ( https://bun.sh/ ). The language isn't exactly in an early stage.
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#78Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#79Earlier quoted context omitted.
I’m a casual user and the 0.16 changes scare me. I tried multiple attempts now, even with full LLM support to upgrade and the result is just a) painful and b) not very good. I have high doubts that the current IO system of 0.16 will make it for another release given the consequences of their choices.
Here's some advice: 1. if you're a casual user (ie you don't follow the development) don't try incomplete APIs that not even the creators of fully know how they are supposed to work (because they're still tinkering with them) also you can't expect docs until the design is somewhat finalized (which is not yet, fyi) 2. llms don't help when trying to make sense of the above (a feature that is not complete, that has no d…
From what I can tell pretty much everything can be broken at any point in time. So really the only actual advise here is not to use the language at all which is not reasonable.
> llms don't help when trying to make sense of the above
That has not been my experience. LLMs were what enabled me to upgrade to 0.16 experimentally at all.
> If you want to try new features before they land in a tagged release, you must engage with the development process at the very least.
No, that is unnecessary gatekeeping. 0.16 will become stable at one point and I don't want to wait until then to figure out what will happen. That's not how I used Rust when it was early (I always also tried nightlies) and that line of thinking just generally does not make any sense to me.
The reality is that Zig has very little desire to stabilize at the moment.