Thanks for the feedback.
Since the JEP lays out the reasons for removing the API I won't repeat
them here.
Anyone needing something like the applet API has been given 8 years of
notice to migrate.
9 years by the time JDK 26 ships and there'll be many years of JDK
support from multiple vendors for releases prior to that.
And as an API Applet is dated.
If I were to want to be able to use Java in a browser via WASM, or
anything else,
I wouldn't re-use the applet API to do it.
-phil.
On 7/22/25 1:36 PM, Anthony Goubard wrote:
Hello,
Since the mailing-list is one of the places to provide feedback, I
wanted provide feedback about JEP 504 <https://openjdk.org/jeps/504>:
Remove the Applet API
Even if the applet plug-in for browsers is not used anymore, there are
other ways applets are used.
I have developed plug-ins for IntelliJ IDEA (& similar JetBrains IDE),
Eclipse and NetBeans to be able to run applets embedded in the IDE.
The plug-ins have reached more than 50,000 downloads since 2021.
All my software (more than 20 Swing applications) are also applets.
They are also available as standalone but as applet, people can run
them embedded in their IDE or in the file manager that I wrote that
also supports running applets.
You also have products like CheerpJ and TeaVM that make (or could
make) possible to run applets embedded in a browser that supports
WASM/WebAssembly.
See the recent top comment in
https://www.reddit.com/r/java/comments/1kxchwf/cheerpj_41_java_in_the_browser_now_supporting/
Also searching for "path:*.java JApplet" results in 14,500 results in
GitHub.
I can understand that you want to get rid of old code that you think
is never used (like AppletInitializer) but I think it's not the case
for the classes Applet, AppletContext, AppletStub and JApplet.
Best regards,
Anthony Goubard
