logoalt Hacker News

kllrnohjtoday at 12:21 AM3 repliesview on HN

> that will let me iterate at the speed of JS or Python with performance of C or Rust.

Didn't Go already do that?

> I am so used to thinking that Zig, Rust, and the likes are only viable in niches where C is viable, but no. not anymore at least - once this linker and incremental compilation on other targets land, Zig will become THE C replacement

Yes, and it will still only be useful in the same niche that C is because the entire philosophy of Zig is to essentially be like C. You're never going to interate at JS/Python speeds with Zig because you'll always be wrangling with memory lifecycles, object lifecycles, etc...

Rust is significantly different.


Replies

dapperdraketoday at 12:53 AM

Go is for the cases where GC works for you (many, many cases).

Zig is for when you need control over the allocator (also many such cases).

bpavuktoday at 8:03 AM

> Didn't Go already do that?

no. GC pauses turn any serious systems work into hell.

> Yes, and it will still only be useful [...]

this does not exclude the possibility of creation of libraries that manage everything for me within their domain of responsibility, such as dvui

show 1 reply
vips7Ltoday at 4:52 AM

Go is a terribly verbose language.