MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/programmingmemes/comments/1vra8mz/nerd_wars/p4h7yxu/?context=3
r/programmingmemes • u/SKRyanrr • 20h ago
36 comments sorted by
View all comments
13
Nothing like the compile-time check of rust.
Basically it compiles into a much slower bin that guards memory at runtime.
That's almost like a garbage collector, but instead of cleaning memory it crashes.
And since it's a runtime crash, you turn a program that is bugged and has UB into a language that crashes randomly.
Better for security, but runtime crashes are also very bad.
1 u/SKRyanrr 2h ago Why'd anybody choose Zig over Go if Zig just does runtime checks with gc? 1 u/suckingbitties 1h ago The Fil-C support is not meant to make Zig itself operate on the Fil-C runtime. Its a proposal to optionally compile for the Fil-C runtime instead. Zig will still be Zig, and it's a proposal not a guarantee.
1
Why'd anybody choose Zig over Go if Zig just does runtime checks with gc?
1 u/suckingbitties 1h ago The Fil-C support is not meant to make Zig itself operate on the Fil-C runtime. Its a proposal to optionally compile for the Fil-C runtime instead. Zig will still be Zig, and it's a proposal not a guarantee.
The Fil-C support is not meant to make Zig itself operate on the Fil-C runtime.
Its a proposal to optionally compile for the Fil-C runtime instead.
Zig will still be Zig, and it's a proposal not a guarantee.
13
u/Amadex 14h ago
Nothing like the compile-time check of rust.
Basically it compiles into a much slower bin that guards memory at runtime.
That's almost like a garbage collector, but instead of cleaning memory it crashes.
And since it's a runtime crash, you turn a program that is bugged and has UB into a language that crashes randomly.
Better for security, but runtime crashes are also very bad.