Fool me once, shame on you.
Fool me twice, shame on me.
Fool me a thousand times, you must be the writer of the JSwing-dokumentation

Idk if somebody already told you this today, so I'll do it just to be safe.

FUCK JAVA SERVER PAGES
FUCK JAVA SERVER FACES
FUCK JSWING
FUCK JQUERY
AND ESPECIALLY FUCK JQUERY UI
FUCK ALL OF THIS OUTDATED SHIT
I'LL NEVER USE IT AFTER SCHOOL, BECAUSE IT'S SHIT!
Repeat after me

S H I T !

For a project day we had to write a game of our choice in Java.

"You should make this game using the JSwing library and make each component a JComponent"

Later I learned you can simply use a Bitmap as a canvas.

NEVER. EVER. BASE. YOUR. GAME. ON. SWING.
It inefficient to the top of my taskmanager. I had to wrap everything with something like a virtual playground where I had to manage everything myself to not roast my cpu.

I had alot more fun debugging hundred lines of C code with print statements than writing that shit

Best way to tell people that JSwing is not suited to make games?

I can't comprehend the fact they draw a grid playfield using JLabels.

Fighting against a occasionally occurring bug, in a networking, multithreading, server-client game.
Thanks to the good excellent front end each client only uses around 20% of my cpu and ~1.3Gb of ram.

Shit happens when you join the development late and your partners code happens on-the-fly.

Maybe redoing it from scratch with something else than JSwing could improve the performanxe slightly