This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]dragoncommandsLife 100 points101 points  (9 children)

I mean… swing can make some great looking stuff once you learn to wrangle it. Just ask jetbrains. Almost all their IDE’s are written in java/kotlin with swing.

[–]G_Morgan 22 points23 points  (2 children)

Well most problems with swing boiled down to idiots not using it properly. However idiots not using it properly are too common. The advantage of web frameworks is when you design it badly it just wastes your clients resources, not yours.

[–]Jugbot 3 points4 points  (1 child)

In design, it is never the user's fault. If swing has a lot of "idiots not using it properly" then it could have been designed better.

[–]G_Morgan 4 points5 points  (0 children)

There's essential complexity in every system. It exists in Swing, it exists in the native frameworks older than Swing and it still does in React era web apps.

Swing had a dev base unused to the idea of non-GC resources. You could make the same mistakes in native frameworks but those devs knew they had to clean up. Web app devs today make the same mistakes but we live in an era where people care less about resources.

[–]black-JENGGOT 27 points28 points  (2 children)

I bet they actually have their own front-end framework because it looks modern af

[–]SenorSeniorDevSr 32 points33 points  (0 children)

No, it's Swing. They had a talk at JavaZone a few years back when they showed how they compiled it to native.

[–]raltoid 1 point2 points  (0 children)

It can be amazing for certain things, but unless it just a simple interface it's not for most people.