News for hackers. Stuff that matters.
Re:Zig breaking change – initial Writergate by lionkor on Friday July 04, 2025 @03:12AM (#44461925)
The killer application case is slow adoption inside ancient C and C++ codebases. That's the angle.
Re:Zig breaking change – initial Writergate by pjmlp on Friday July 04, 2025 @03:55AM (#44462227)
It hardly brings anything new to the table in such cases, given its approach to safety.

Most of it you can already get in C and C++, by using the tools that have in the market for the last 30 years.

Re:Zig breaking change – initial Writergate by lewdwig on Friday July 04, 2025 @04:37AM (#44462478)
And yet C/C++ developers have mostly spent the last 30 years not using those tools which is why safer successors to C and C++ appeared.
Re:Zig breaking change – initial Writergate by pjmlp on Friday July 04, 2025 @07:29AM (#44463562)
Zig is as safe as Modula-2 or Object Pascal, not the turning point of something like Swift or Rust.
Re:Zig breaking change – initial Writergate by detaro on Friday July 04, 2025 @04:41AM (#44462505)
I think pjmlps point is that Zig is not adding enough to be one of those safer successors.
Re:Zig breaking change – initial Writergate by lionkor on Friday July 04, 2025 @06:42AM (#44463307)
It brings a lot of nice features, the potential for a healthier ecosystem, a unified build system, explicit allocators, explicit casts, and so on.
Re:Zig breaking change – initial Writergate by pjmlp on Friday July 04, 2025 @07:30AM (#44463569)
Ecosystems sell languages, not the other way around.
Re:Zig breaking change – initial Writergate by lionkor on Friday July 04, 2025 @07:02PM (#44468664)
Yes, and you can use Zig in the C and C++ ecosystems, that's my point
Re:Zig breaking change – initial Writergate by pjmlp on Saturday July 05, 2025 @06:00AM (#44471514)
For what though, what is the selling point to have IT accept it on the allowed toolchains.