News for hackers. Stuff that matters.

A comment on How (memory) safe is Zig? (2021). Parent comment

Re:How (memory) safe is Zig? (2021) by ajross on Tuesday May 13, 2025 @08:19PM (#43979383)
Weird that Swift is your totem for "managed/collected runtime" and not Java (or C#/.NET, or Go, or even Javascript). I mean, it fits the bill, but it's hardly the best didactic choice.
[ Parent | on HN ]
Re:How (memory) safe is Zig? (2021) by saagarjha on Wednesday May 14, 2025 @04:32AM (#43982240)
I don't think they said anything about that?
[ Parent | on HN ]
Re:How (memory) safe is Zig? (2021) by ajross on Wednesday May 14, 2025 @11:30AM (#43985756)
The point was that basically no one knows Swift, and everyone knows Java. If you want to point out a memory safe language in the "managed garbage-collected runtime" family, you probably shouldn't pick Swift.
[ Parent | on HN ]
Re:How (memory) safe is Zig? (2021) by orobio on Wednesday May 14, 2025 @04:03PM (#43988616)
I wouldn’t put Swift in the same ‘managed garbage-collected runtime’ family as Java, C#/.NET, Go, and Javascript, so maybe they weren’t trying to do what you think.

Swift is more like a native systems programming language that makes it easy to trade performance for ergonomics (and does so by default).

[ Parent | on HN ]