kristoff_it

7 ms·

61.
by kristoff_it 1y ago
The longevity of donation platforms is a major concern for us and GitHub has not been good in that sense. GitHub Sponsors has not seen a single improvement in the years after its launch (despite us and other organizations chatting with GitH
62.
by kristoff_it 1y ago
> Does the Zig Foundation have a policy against corporate sponsors? Not at all. We would be definitely open & happy to learn that one of the big companies are using Zig and would be interested in supporting us. (but we don't pla
63.
by kristoff_it 1y ago
So in practice money is effectively being donated (donating hw is not free) to be spent on CI, not very differently than in our case, but you're delighted to not know the numbers and like to imagine it's $0. Ok :^)
64.
by kristoff_it 1y ago
It's also the one-time cost of buying some machines, not just renting.
65.
by kristoff_it 1y ago
I've added more explanatory comments in the new template that ships with 0.15.1, also you might be interested in this video https://www.youtube.com/watch?v=jy7w_7JZYyw
66.
by kristoff_it 1y ago
Zig is not really a handmade project, case in point both Andrew and I are blocked on social media by the two gods of the handmade movement (casey and john) and, according to their die hard fans, Andrew gave a talk at the last handmade confe
67.
by kristoff_it 1y ago
> The key problem with Zig nowadays is how much of its community and adoption is driven by anti-Rust sentiment. As a result, while Rust puts beginner onboarding and documentation at the center of its culture, as opposed to the “C neckbea
68.
by kristoff_it 1y ago
> I think the argument is that it is also extremely difficult to write low level libraries in Zig, just as it is in C. This has been not my experience at all in the ~6 years I've been writing Zig. I started having very little experi
69.
by kristoff_it 1y ago
The Reader/Writer changes are perfectly compatible with the upcoming async I/O stuff and you won't need to change any code that just deals with streams. No promises about potential future changes though :^)
70.
by kristoff_it 1y ago
Is this going to solve the combinatorial explosion of pre-building native dependencies for every possible target? Python should get rid of its training wheels :^) https://kristoff.it/blog/python-training-wheels/
71.
by kristoff_it 1y ago
We plan to have in Zig a testing `Io` implementation that will potentially use fuzzing to stress test your code under a concurrent execution model. That said, I think a key insight is that we expect most of the library code out there to not
72.
by kristoff_it 1y ago
> If the client were to execute before the server and fail to connect (the server is not running to accept the connection) then your system has failed, the server will run later and be waiting forever on a client who's already died.
73.
by kristoff_it 1y ago
That eventually the server and the client are able to connect.
74.
by kristoff_it 1y ago
> The contrasted example which is still concurrent but not asynchronous is the client and server one Quote from the post where the opposite is stated: > With these definitions in hand, here’s a better description of the two code snipp
75.
by kristoff_it 1y ago
>I kind of think the author simply pulled the concept of yielding execution out of the definition of concurrency and into this new "asynchrony" term. Quote from the article where the exact opposite is stated: > (and task swi
76.
Asynchrony is not concurrency(kristoff.it)
311 points by kristoff_it 1y ago|216 comments
77.
by kristoff_it 1y ago
Allocator is an interface so you write library code only once, and then the caller decides which concrete implementation to use. There's cases where you do want to change your code based on the expectation that you will be provided a s
78.
by kristoff_it 1y ago
If you want to go down that route, any function that has, or doesn't have, any given resource is colored then. fn foo(db: *Db) !void { ... } fn bar() !void { ... } Would you consider `foo` a blue function and `bar` a red fun
79.
by kristoff_it 1y ago
My mistake, I should have said Python then.
80.
by kristoff_it 1y ago
> If this doesn't make the argument that Zig has certainly not defeated function coloring, I don't know what would. if you're opting into stackless coroutines then yeah you're opting into their viral nature, but the p
81.
by kristoff_it 1y ago
Correct, which is also something that you want to do when creating Reader / Writer chains.
82.
by kristoff_it 1y ago
> but IMHO people who sit down for a bit and think through the issue come to the same conclusion you have - Function coloring isn't a problem in practice. I dunno man, have you seen people complain about async virality in Rust being
83.
by kristoff_it 1y ago
while not really idiomatic, as long as you let the user define the Io instance (eg with some kind of init function), then it doesn't really matter how that value is accessed within the library itself. that's why this isn't re
84.
by kristoff_it 1y ago
we do build internal consensus before publishing articles like this one, or doing other public communication.
85.
by kristoff_it 1y ago
I should have specified that better, of course async and await can be lowered to different things (that's what Zig does afterall), what I wanted to say is that that's how it works in general. JS is a good counter example, but for
86.
by kristoff_it 1y ago
> (And before anyone mentions it, devirtualization is a myth, sorry) In Zig it's going to be a language feature, thanks to its single unit compilation model. https://github.com/ziglang/zig/issues/23367
87.
by kristoff_it 1y ago
mlugg is in the Zig core team
88.
by kristoff_it 1y ago
Here's a trick to make every function red (or blue? I'm colorblind, you decide): var io: std.Io = undefined; pub fn main() !void { var impl = ...; io = impl.io(); } Just put io in a global variable
89.
by kristoff_it 1y ago
That's pretty much what it is, it's a reaction to an implosion that happened last year in the Handmade Network related to the Handmade Seattle conference which caused the conference organizer and the community leads to go separate
90.
Orca Build System(orca-app.dev)
3 points by kristoff_it 1y ago|0 comments

More ›