I see all this code where people import all the necessary AWT stuff and use BufferStartegy but their main component utilises JFrame instead of Frame. Whats the advantage? Is it for windowed apps? Is there an advantage when running full screen exclusive mode?
I leave it up to you to decide, but the fact is that other one creates tons and metric tons of overhead, is slow and starts/activates unnecessary threads, and supports lightweight components…
dont be confused by code samples,
code samples on the web usually use JFrame, simply because it requires fewer lines of code to get an operating app.
For your own apps, you should always use a Frame.
(for the reasons Captain said…)
JFrame extends Frame as a root for Swing applications. It introduces a basic infrastructure for the swing component hierarchy, menus, tooltips etc. and establishes smart repaint strategies (lightweight rendering) for them.
I cannot see where it creates new threads and why that should be evil.
If you use Swing, there no way around it.