To quote you: “they don’t want to rewrite everything” …
Writing Rust often implies major refactoring and it takes so much time to write that your requests go: “pewf” closed due to the amount of effort it takes.
Anyway, been there, done that! Zig is probably the real future; it’s a joy to write, it compiles fast, clear to read, and safe.
It has shared libraries and a proper integration with existing C/CPP code base.
You should try it, that’s an amazing language with a real potential to replace the legacy.
That’s what I am saying.
To quote you: “they don’t want to rewrite everything” …
Writing Rust often implies major refactoring and it takes so much time to write that your requests go: “pewf” closed due to the amount of effort it takes.
Anyway, been there, done that! Zig is probably the real future; it’s a joy to write, it compiles fast, clear to read, and safe.
It has shared libraries and a proper integration with existing C/CPP code base.
You should try it, that’s an amazing language with a real potential to replace the legacy.
I dunno man… I’m not sure I’m so keen on a language that prides itself on not having macros
Comptime replaces macros/reflection.
It’s basically Zig code that runs at compile time in your code…
No other “weird” language to learn; it’s zig all the way. What you would have written in macro is written in zig comptime.
Even the build system is zig…
Same for generics, it’s comptime…