Viewing profile — kristoff_it

(reposting my comment from lobsters) For anybody reading, the project tracks new Zig to get all the new async I/O goodies but was hit by some regressions in Zig's translate-c becau…

Yes it was never attempted, the whole communication on social media about the AI policy was completely detached from the reality of the engineering work being done on either side.

The people who originally worked on Bun themselves would disagree with your point (but their situation was based on the premise that they did not take the steps required to leverag…

To me the most interesting fact about this fork is that it has proven that Bun could have had fast builds all along. To be fair, there are caveats still in place today: Zig increme…

That is a 100% on point analysis, there was a lot of hype around Bun since the beginning when it was an invite only project. Arguably that same interest is what got Jarred VC fundi…

> Writing memory safe code in unsafe languages requires global reasoning If you learn how to use arena allocators and in general use modern techniques, you don't need global reason…

Thanks, yeah Andrew gave a pretty good interview to the JetBrains people recently https://www.youtube.com/watch?v=iqddnwKF8HQ

I think you will be surprised by how many developers do not have this same list of priorities (or in that order) when developing software. I posted this link at the same time when …

The truth is a bit of everything, bun being a messy codebase written primarily with "move fast and break things" in mind, cultural divergence between Bun and the Zig community, and…

> I imagine it's a difficult time to be a Zig developer. In some ways it always has been, the community was 'born' in the middle of the pandemic, then for a long time there was a c…

That is correct, this blog post is about understanding the priority of various subgoals and the ultimate goal (creating useful software). Memory-safety is important but overfitting…

trying to make good software :^)

That is the opposite of what's going on, read this https://kristoff.it/blog/contributor-poker-and-ai/

The problem statement is clear to everybody. > For decades, code contributions have been how open source projects learned who to trust. People would show up, do the work, take resp…

Another Zig GUI project that people might be interested in is DVUI: https://github.com/david-vanderson/dvui

It's not Future.await that is special per se, it's that it (Future.await) will have in it somewhere either in its body or in another function that it calls in turn, a use of `suspe…

None of it, we've been working on this stuff for a long time already, scroll the devlog backwards, you will find plenty of entries on that topic. It's the opposite: people have bec…

> If so, does that mean that every function in zig is a stackless coroutine? No and yes. If you're using Io.Threaded, then the concurrency model is multithreading and calling Futur…

A vtable indirection is essentially free when you're going to perform a syscall. What matters is that the buffer is above the vtable (which is already the case for the current impl…

> You are supposed to do as much programming as you can in the high level language, and only drop into the low level language as needed. I think that's a neat idea, but in the reve…