11 ms·
A lot of cruft has been split into modules, so you no longer have AWT/Swing/smartcardio/etc. in your classpath unless you want it. A lot of cruft is still ther
by tadfisher 4y ago
A lot of cruft has been split into modules, so you no longer have AWT/Swing/smartcardio/etc. in your classpath unless you want it.
A lot of cruft is still there; Date, File, InputStream/OutputStream, sun.misc.Unsafe, and the entire legacy reflection API are the bunch that stick out to me. Newer releases are actively mentioning their legacy status in documentation, and there are certainly JEPs to remove them or make them opt-in/opt-out.
If you look at OpenJDK internals, or even the foreign function/memory APIs as described in the article, it looks almost nothing like the Java I learned on and wrote for several years. Most of the Panama API is piggybacking on additions to the language made post-JDK9 or so, such as MethodHandle, VarHandle and @PolymorphicSignature methods. So I'd say the language and runtime is evolving nicely, even under the thumb of Oracle.
- ahtihn 4y ago> InputStream/OutputStream I think I missed the announcement of those being "legacy" APIs? They show up all over the place including in libraries, what is the replacement?
- tadfisher 4y agoThe modern versions of these are Channel APIs in java.nio. The "N" in nio stands for "New" even though it was introduced in Java 1.4.
- kaba0 4y agoBut the old ones aren’t superseded the same way Date is, though. You are perfectly fine using them and in fact will perform similarly well due to Loom (which has actually reimplemented them on top of async APIs)
- ohgodplsno 4y ago>legacy reflection API Did I miss something somewhere ? java.lang.reflect is still the standard way of doing Reflection.
- TravelPiglet 4y agoYou can use Method Handles now for better performance in a lot of cases