They might be memory safe, but not safe from drama 😂

ok claude, fix memory management. make no mistake !

You are right. Memory management is the hardest problem in programming today. I can hardly remember what and/or why I wrote the code I did a month ago.

Haskell be still compiling till you release the next video; the smarter the language, the longer it takes to get you the binary!

Long time C/C++ developer, the Zig proposal still doesn't like it solve the problem of catching memory problems at the earliest point in development... before it runs.  You still have to handle those panics at run time at some point.  Also, no one accounts for the client's time tracking down those memory issues after the fact even with ASAN or Fil-C or whatever dyanmic checker is added and they could happened at odd times.

I really like pattern matching and error handling in rust

Maybe I completely missed what Fil-C actually is.
But I feel that this "safe mode" in Zig would be more of a debug mode than anything else.
Once your program runs long enough without panicking, you can compile it in regular release mode and avoid the runtime penalty while being reasonably sure that you don't have many memory-related bugs.

I use fil-c a lot, just compile with fil-c, run your fuzzing tests in your CI with it, find issues, fix it, but run the program raw dog mode.

Golang user :

👀

Adding a runtime to zig defeats the entire purpose of zig and at that point just use go. They could do something similar to rust dyn and smart pointers, which has a scoped overhead, but at that point the language is going to add complexity, which explicitly goes against the goal of "Focus on debugging your application rather than debugging your programming language knowledge."

Wait, is Zig's proposal just a GC ?

Mom and Dad are fighting again 😭

Polonius is a character in William Shakespeare's play Hamlet.
Polonius's most famous lines are found in Act 1 Scene 3 ("Neither a borrower nor a lender be"; "To thine own self be true").
So it makes a very good name for  the borrow checker project :)

Well... Fil-C goals are mostly achieved with libc/libstdc++ library hardening flags. The newer gcc version offer -fhardened flag which enables a preset hardened flags for the compiler and the library code.

zig: you took everything from me!!
rust: i dont even know who you are...

"many languages trying to solve it ..." And throwing there the JS logo ... It's like fixing road safety by a universal 20 km/h speed lilit

Those afraid of bears should maybe not visit the forest.

me, odin user, watching this with popcorn

always good to see dan

To get the actual context watch talks in "Software Should Work" conference both from A. Kelley and Fil-C author. So probably they had some offline meeting and aligned.