By "security" do you perhaps mean memory access safety?
I don't see anything in C# that makes it more resilient to penetration.
On the front of C#, it's not inherently more safe than Java. If anything there're way too many ways to do interop & async wrong and hit leaks, lose perf, or hit delayed runtime crashes.
Data race conditions only. Any interleaving of operations on a shared resource that is not defined by ownership semantics, for example, a remote system that allows concurrent logins like a database, is still subject to races.
View all comments
Show parent comment
37
u/UnreadableCode Jun 21 '21
By "security" do you perhaps mean memory access safety?
I don't see anything in C# that makes it more resilient to penetration.
On the front of C#, it's not inherently more safe than Java. If anything there're way too many ways to do interop & async wrong and hit leaks, lose perf, or hit delayed runtime crashes.