vitaminCPP

This is great. It really showcases zig's dedication to quality, IMO.

I wish they took the time to communicate the intricacies of their toolchain.

Some things I think are remarkable:

Contrary to Rust, zig allows to cross-compile to MacOS. I think this implies that zig needed to build a custom linker!

Regarding libc:

- On Linux libc is not required because zig is using syscalls directly

- On MacOS libc is required because of the lack of stable abi

- On Windows libc is not required because zig links to windows kernel dll.

To my understanding, this implies that a compiled zig program will work across all linux distributions!

For C integration, I'm not knowledgeable enough to fully appreciate the work being done. but the fact that the cross-compiling also works out-of-box is mind-blowing to me.

This is great. It really showcases zig's dedication to quality, IMO. I wish they took the time to communicate the intricacies of their toolchain.

Some things I think are remarkable:

Contrary to Rust, zig allows to cross-compile to MacOS. I think this implies that zig needed to build a custom linker!

Regarding libc:

- On Linux libc is not required because zig is using syscalls directly - On MacOS libc is required because of the lack of stable abi - On Windows libc is not required because zig links to windows kernel dll.

To my understanding, this implies that a compiled zig program will work across all linux distributions!

For C integration, I'm not knowledgeable enough to fully appreciate the work being done. but the fact that the cross-compiling also works out-of-box is mind-blowing to me.

Is there a video of the talk somewhere ?

I prefer recording over slides.

Great article.

It can frustrating to see members from the Rust community just assume that RAII is a good idea; completly dismissing that this debate has been going on for the last 3 decades in system programming community.

I really like this mentality.

I whish there was more ressource to learn this "low-level" approached to web developpement.

SQLite would require a file system. Embedded systems typically do not have this.

> "ggc utility"

Does anybody know what this is? Google won't help.

Same

This is match my experiences.

Saddly, bad middle manager wants to hire a yesman (or women). Not an experienced engineer that will challenge them by highlighting to upper management the project technical debt, the lack of tests or the broken CD pipeline.

I don't know where you are from, but in Canada there's a clear distinction between those 2 degres.

it's a joke. Obviously, when you're a compiler engineer, creating a progress bar is not a great demonstration of your skill.

Hey Jarred; Nice to see you here.

Great work on Bun. Excited to see the future of your project.

Insight full comments. Thanks for sharing.

Does anybody know about a unit library in C?

> Aside: I really hate how the nullprogram site linked seems allergic to type-safety.

Could you give us an example, I'm not sure what you refering to.

Any details on this ? I try building this in the past, without success.

I'm interested about what features worked for you.

> No other language I know has an equivalent tool.

I completely agree: this has been my experience as well.

At the moment, Zig and Rust are the most exciting places to look, IMO.

Brian Douglas is certainly one of the great teacher of control. That said, this books is, to my knowledge, a incomplete and abandoned project.

I would recommend checking it's YouTube channel instead.

While the title may say otherwise, the article is worth a read just for the talks recommandation.

Can you share more details? This is a world I know nothing about.

> double blind

Ah!

This is why I like this forum: Understanding brain biology with a Electron's app RAM consumption analogy.

This is a great selection. Thanks for sharing.

If one of your requierements is performance, ressource efficiancy and responsiveness, memory layout is the opposite of irrelevant.

I can't imagine living in a 3rd world country with today's electron's catastrophy.

This is good. It made me think at the "tutorial hell" concept.

Thanks. I realized that there are several types of MMU. I was thinking of the simple MMU (on 32bit MCU) that limit memory access. Not the one that provides the illusion of virtual addressing.

thanks for sharing

> Because Linux-capable application processors have a memory management unit, *alloc() calls execute swiftly and reliably. Physical memory is only reserved (faulted in) when you actually access a memory location. Memory fragmentation is much less an issue since Linux frees and reorganizes pages behind the scenes.

This paragraph is confusing to me.

- How would a MMU help for malloc to execute "swiftly and reliably" ?

- What does "actually access a memory location" implies exactly?

- "since Linux frees and reorganizes pages behind the scenes": Is this not what people dislike from malloc? That it's none deterministic?

This is short and excellent. Thanks for sharing.

I wish Mr. Stoller took more time on this:

> The Federal Aviation Administration, having outsourced much of its own regulatory capacity to Boeing, didn’t know what was going on, and Boeing didn’t tell airlines and pilots about the new and crucial safety procedures.

This seems like big deal to me.