Is it frowned upon to make Java applications as applets if they are not going to be embedded?

There's a standalone appletviewer, but AFAIK that only comes with the JDK - not good for end users. And if you run it in a browser without a surrounding webpage, you still have a useless and (to the user) confusing browser window around it.

I don't see any advantages apart from the ability to embed them in webpages. Most importantly, applets run in a sandbox per default, and thus are very restricted in what they can do. And what do you mean with an applet "never going to be embedded"?

How are you going to run it then? There's a standalone appletviewer, but AFAIK that only comes with the JDK - not good for end users. And if you run it in a browser without a surrounding webpage, you still have a useless and (to the user) confusing browser window around it.

Applets can be launched free floating using JWS. Having said that, I agree with the general thrust of your post. Avoid applets unless they have to be embedded.

– Andrew Thompson Aug 28 '10 at 9:48 I don't know, it just seems like there is a lot less stuff to import and figure out when setting up the framework of an application when you use an applet. Also, when I said "never embedded" I meant never embedded into a web page, which to my understanding is what applets are typically used for. – typoknig Aug 28 '10 at 18:45.

An applet just has a different execution environment than a stand alone application with a main(...). Which one to use, depends on what you need it to do. There is nothing wrong with supporting both the applet and application environment.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.