Comments by "" (@pierreollivier1) on "The Plight Of Cobol Mainframe Programmers" video.

  1.  @CamaradaArdi  There is already TigerBeetle written in Zig which is not a banking system but a transaction data base, no matter how young a language is if your team of engineers is convinced it's a good choice than there is not much to say. Yes Zig is young, and it will absolutely break and change as time goes. But I heavily doubt that the fundamentals of the language are going to chance drastically. Zig is most certainly going to be the future C replacement, for doing what you would have done in C. And Rust is going to replace or at least take some of the stuff that's made in C++, to be made in Rust. Rust is great but in application where speed is important, I think you are better off using Zig, because the assembly is much more predictable, and all of the language design revolves around giving all the facilities for programmers to manage memory and achieve 80% of the safety that Rust offers. In Rust you can indirectly manage memory, or you can manage it with a good granularity, but it's not exactly it's strong selling point and this level of manual memory management, while absolutely feasible falls into the probably bad idea. Rust is a language that offers an amazing performance/abstraction/safety ratio, but just because it's amazing doesn't mean that it can do it all. And in my humble opinion if you want the finest granularity without hand writing assembly than Zig is definitely the language that offers the best ratio of control/predictability/safety.
    1