5 ms·
This is why I've pretty well decided that Swing on the JVM is the way to go. I have some confidence that a jar I compile today for a Swing app is going to work
by madhadron 6y ago
This is why I've pretty well decided that Swing on the JVM is the way to go. I have some confidence that a jar I compile today for a Swing app is going to work in ten years.
- rdsubhas 6y agoThat's really weird to hear. If you build an app with GTK3 today, it's still going to work for 10 years. It's compiled into the application, it's not a runtime API. Even if you upgrade GNOME to some futuristic 10 year version, the GTK3 compiled app will just continue to work fine. The parent thread is comparing a runtime API (Win32) with a compile-time library (GTK).
- seba_dos1 6y agoAs a case in point, I just played with an unmodified GTK2 mapping app (FoxtrotGPS) from Openmoko times (2008) on my Librem 5 phone running modern Wayland shell (phosh). Wasn't crisp because GTK2 doesn't support hidpi, and touch support could be better, but worked very well otherwise.
- madhadron 6y agoIf I build a static binary for each platform I want to release it on and we don't have another a.out to elf transition... Oh, and building it will end up needing a special environment as opposed to the stock JDK.
- MaxBarraclough 6y agoWhy would you use Swing over JavaFX, for new projects?
- madhadron 6y agoSwing is part of the core JDK and fully mature.
- MaxBarraclough 6y agoJavaFX has been mature for years now. It's true though that it's been 'spun out' into OpenJFX.