a case for reconsidering JEP 398: Deprecate the Applet API for Removal

mark.yagnatinsky at barclays.com mark.yagnatinsky at barclays.com
Tue Apr 6 14:13:31 UTC 2021


> Java loads classes lazily, so depending on how the application is coded, it may not an issue at all

I think the usual pattern is

class MyLittleApp extends Applet {
	public static void main(String... args) {
		invokeLater(some runnable that creates the main window);
	}
}

And I think here Java has to load Applet eagerly because Applet might have a static init block.

And yes, I agree that this is not an issue until 2030 or so.
But if I wait until then to speak up, the response will likely be:
"Why didn't you say anything when we were making these decisions?  You had a whole decade."

And yes, writing an agent would work if the application is popular enough.
Lots of things are possible for applications that are popular enough.
But there's a long tail of things that are not popular enough.

In my first email I included as an example some Java code that some professor wrote as a companion to a book on computational geometry in C.
(Yes, the book was about C; the Java code is just "bonus content".)
I expect that once that professor retires, this code will have zero maintainers.

My concern is for this "long tail" of combo desktop apps / java applets that are not popular at all, but still appreciated by their few users.

Thoughts?

_________________________________________________________________________________________________________________________________________________________________________________________________________________________________
“This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer.

For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; https://www.investmentbank.barclays.com/disclosures/barclays-global-markets-disclosures.html regarding our standard terms for the Investment Bank of Barclays where we trade with you in principal-to-principal wholesale markets transactions; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com.”  
_________________________________________________________________________________________________________________________________________________________________________________________________________________________________
If you are incorporated or operating in Australia, please see https://www.home.barclays/disclosures/importantapacdisclosures.html for important disclosure.
_________________________________________________________________________________________________________________________________________________________________________________________________________________________________
How we use personal information  see our privacy notice https://www.investmentbank.barclays.com/disclosures/personalinformationuse.html 
_________________________________________________________________________________________________________________________________________________________________________________________________________________________________


More information about the jdk-dev mailing list