Sysadmin for 15 years here though, Java was always a problem. The version wasn't always the worst bit, but it was always an exercise in frustration.
Mostly security controls to blame, but I have had so many issues across so many systems that I cannot stand by and let you claim this is FUD about Java.
the .NET applets are also a problem (because who has a compatible IE version?), but they worked more consistently than the Java ones back in the day.
The HTML5 ones are the only ones that seem to work consistently; but that could be biased as HTML5 is much newer, so BMCs implementing that might be updated with more regularity. (or be more modern hardware)
I've seen multiple vendors with problematic code that didn't work with newer Java versions.
This is by no means meant to bash Java. Some non-Java BMCs can be horrible as well (e.g. require many TCP ports in a firewall/tunnel unfriendly way or require SSH with old algorithms that are no longer enabled by default, or telnet..)
1. Downloads the data from the IPMI interface
2. Modifies the files to run locally
3. Writes out a Java configuration with weak security settings so that TLS works with the deprecated ciphers.
4. Fires off a socat instance to redirect the localhost ports to the remote IPMI device.
5. Starts appletviewer locally.
Great fun writing that. Thank god we decomissioned the last X7 based storage appliances a while ago...