<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
Thanks for the feedback.<br>
<br>
Since the JEP lays out the reasons for removing the API I won't
repeat them here.<br>
<br>
Anyone needing something like the applet API has been given 8 years
of notice to migrate.<br>
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. <br>
<br>
And as an API Applet is dated.<br>
If I were to want to be able to use Java in a browser via WASM, or
anything else,<br>
I wouldn't re-use the applet API to do it. <br>
<br>
-phil.<br>
<br>
<br>
<div class="moz-cite-prefix">On 7/22/25 1:36 PM, Anthony Goubard
wrote:<br>
</div>
<blockquote type="cite" cite="mid:CANsEkGvDZCcPPR1-PEghAc5XFzaOAxvUnq4um5G9ykwirv=x2A@mail.gmail.com">
<div dir="ltr">Hello,<br>
<br>
Since the mailing-list is one of the places to provide feedback,
I wanted provide feedback about <a href="https://openjdk.org/jeps/504" moz-do-not-send="true">JEP
504</a>: Remove the Applet API<br>
<br>
Even if the applet plug-in for browsers is not used anymore,
there are other ways applets are used.<br>
<br>
I have developed plug-ins for IntelliJ IDEA (& similar
JetBrains IDE), Eclipse and NetBeans to be able to run applets
embedded in the IDE.<br>
The plug-ins have reached more than 50,000 downloads since 2021.<br>
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.<br>
<br>
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.<br>
See the recent top comment in <a href="https://www.reddit.com/r/java/comments/1kxchwf/cheerpj_41_java_in_the_browser_now_supporting/" moz-do-not-send="true" class="moz-txt-link-freetext">https://www.reddit.com/r/java/comments/1kxchwf/cheerpj_41_java_in_the_browser_now_supporting/</a>
<div><br>
Also searching for "path:*.java JApplet" results in 14,500
results in GitHub.<br>
<br>
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.<br>
<br>
Best regards,<br>
Anthony Goubard</div>
</div>
</blockquote>
<br>
</body>
</html>