Zig – io_uring and Grand Central Dispatch std.Io implementations landed
1–10 of 315 posts
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#2[flagged]
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#3[flagged]
Can you elaborate? Zig has a lot of traction already.
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#4[flagged]
I feel like this is doomerism with high bias - i'm sorry but there is nothing founded here ; for all I know ; if Zig is able to put only one good reason to be used - some people will use it and not care - however this is a purely logical statement and I do not know of Zig so I might be blind here.
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#5[flagged]
Instead of debating for years (like other languages), zig just tries things out. Worst case you can always rollback changes.
IMO best APIs and designs are those that are battle tested by end users, not won in an argument war during committee meetings.
This makes zig unique. It's fun to use and it stays fresh.
You can always just stay on older version of zig. But if you choose to update to newer version, you get new tools to make your code tidier/faster.
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#6> Both of these are based on userspace stack switching, sometimes called “fibers”, “stackful coroutines”, or “green threads”.
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#7> Both of these are based on userspace stack switching, sometimes called “fibers”, “stackful coroutines”, or “green threads”.
[deleted]
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#8[flagged]
Instead of debating for years (like other languages), zig just tries things out. Worst case you can always rollback changes. IMO best APIs and designs are those that are battle tested by end users, not won in an argument war during committee meetings. This makes zig unique. It's fun to use and it stays fresh. You can always just stay on older version of zig. But if you choose to update to newer version, you get new t…
This is my favourite way to iterate, but the hard lesson is at some point after trying a bunch of things comes the Big Cleanup (tm). Is that a potential issue for this with Zig?
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#9[flagged]
Instead of debating for years (like other languages), zig just tries things out. Worst case you can always rollback changes. IMO best APIs and designs are those that are battle tested by end users, not won in an argument war during committee meetings. This makes zig unique. It's fun to use and it stays fresh. You can always just stay on older version of zig. But if you choose to update to newer version, you get new t…
> Instead of debating for years (like other languages), zig just tries things out.
So did Rust pre-1.0
Stability guarantees are a pain in the neck. You can't just break other people's code willy nilly.
> This makes zig unique. It's fun to use and it stays fresh.
You mean like how Rust tried green threads pre-1.0? Rust gave up this one up because it made runtime too unwieldy for embedded devices.
Re: Zig – io_uring and Grand Central Dispatch std.Io implementations landed
#10[flagged]
There are high profile apps written in Zig, Bun (bought by Anthropic) and Ghostty also Uber use it. What apps are written in Jai or Odin.