Java is the top, C# is the bottom. The Java language designers consider unsigned integers harmful (and this). They’re basically saying “You could hurt yourself with this so we’re taking it away.” I find that patronizing and disrespectful. On the other hand C# and Go tell you, “Yo bro, doing pointer math and direct memory manipulation is not safe, but I’m not gonna stop you.”
I must admit, I’ve been a C# developer for a few years now and I don’t think I’ve every messed around with “unsafe” or even seen it used lol, now I really wanna try it.
I love that about C#. It’s safe and managed, but if you need the unsafe features for performance etc, then they’re available. It’s the best if both worlds, imo.
Java is the top, C# is the bottom. The Java language designers consider unsigned integers harmful (and this). They’re basically saying “You could hurt yourself with this so we’re taking it away.” I find that patronizing and disrespectful. On the other hand C# and Go tell you, “Yo bro, doing pointer math and direct memory manipulation is not safe, but I’m not gonna stop you.”
It sounds like you’re thinking of C++ rather than C#, no?
I’m talking about C#'s unsafe keyword. It lets you do pointer shenanigans.
I must admit, I’ve been a C# developer for a few years now and I don’t think I’ve every messed around with “unsafe” or even seen it used lol, now I really wanna try it.
I love that about C#. It’s safe and managed, but if you need the unsafe features for performance etc, then they’re available. It’s the best if both worlds, imo.