>>32
You have memory safety for one. You can at least catch a generic exception at the base of root routine and restart the application and log a stack trace if something terrible happens. That's better than the segfault (at best) or memory corruption (at worst) that comes with C and C++. It's not the as good as an application that is proven correct, but there are static code analysis tools for that.
If
>>30 is talking about an actually strongly typed language, then I would partially agree. But if
>>30 is talking about C or C++ that then
>>30 should join
>>29 and
>>25 in going back to /g/ and continue spreading their ignorance there.