No amount of sabotage from old entrenched maintainers is going to stop the world from moving forward towards memory-safe languages.
Jesus fucking insufferable Christ… Saying shit like this, given C has been in use for 50 years and is still in very wide use today, and given the vast number of languages that have come and gone over this period, it’s just incredible.
Especially as there’s D, a language that when used in betterC mode, is on-par with C, minus the archaic precompiler, which is replaced with very powerful metaprogramming capabilities.
D didn’t catch on for many good reasons… And it never will. Zig has way more momentum (and it better!) as a “better C”, and obviously the main draw of Rust is memory safety without GC which D doesn’t have.
Jesus fucking insufferable Christ… Saying shit like this, given C has been in use for 50 years and is still in very wide use today, and given the vast number of languages that have come and gone over this period, it’s just incredible.
Probably what all the horse people said when cars were invented.
I would’t trade a good horse for an early car. Maybe a model T.
The horse-car analogies rarely achieve what you want them to, especially in situations where we don’t have the benefit of hindsight.
More akin to Elon insisting the cybertruck is the way of the future, and people just keep buying Rivians and internal combustion vehicles.
Especially as there’s D, a language that when used in betterC mode, is on-par with C, minus the archaic precompiler, which is replaced with very powerful metaprogramming capabilities.
D didn’t catch on for many good reasons… And it never will. Zig has way more momentum (and it better!) as a “better C”, and obviously the main draw of Rust is memory safety without GC which D doesn’t have.
D has a way for GC free operation, the easiest way is by using it in BetterC mode. The harder way is writing your own runtime without a GC.
Yes but that isn’t memory safe.