Ok, so basically every single “safe” language seems to have an “unsafe” - which seems to be objectively worse than C and C++ 😳
37
20
168
Conversation
Replying to
I'd say that most developers don't use it and don't need it. "Unsafe" is mostly used by library developers. I rarely use it myself.
2
3
Java sun.misc.Unsafe isn't part of the standard language and is being gradually deprecated / phased out. A lot of libraries are phasing it out. Here's one that I use in one of my projects where it was removed in the past month:
github.com/ben-manes/caff
It's not super pervasive.
1
4
openjdk.java.net/jeps/193 is a major example of how it's being phased out and is what replaced it in that library.
Java was pretty careful to always consider Unsafe non-standard and strongly discouraged using it. It's also not available in all implementations / environments, etc.
1
2
Everything in the sun.* is non-standard, i.e. it's part of OpenJDK and derivatives rather than part of standard Java.
docs.oracle.com/en/java/javase is another common example of a library from there. It's a decent little multi-threaded HTTP library. It works really well behind nginx.