Earlier quoted context omitted.
Can you explain why it's so hard? I've had a lot better luck running Java apps than Python.
Not the parent but: Java has a long tradition of reimplementing things in Java rather than relying on system libraries. Everything from OpenSSL to tzinfo to libpng has its own Java implementation, entirely separate from anything else on the system.
The decline and fall of Java on the desktop
31–40 of 362 posts
Re: The decline and fall of Java on the desktop
#32Java Swing still lets you make native-looking-and-feeling apps (with some care). I don't know of any new GUI frameworks that let you do the same. I consider this a killer-feature of the framework. It's also very fast, backed by OpenGL and DirectX. It also ships with source code and isn't declarative, so it's trivial to step into as a means to debug why your code isn't working.
Interesting, I'm not aware of any Java app that truly feels or looks native. I guess that there is definitely some selection biais, but do you have any examples of native-like Java Swing apps?
Re: The decline and fall of Java on the desktop
#33Java used to be a slowly rising language and set of platforms with benevolent oversight from SUN and at least the outlook that it was one of a few things you might want to add after Microsoft's Windows or Apple's OS (Macintosh or later OSX).
Then Oracle bought SUN and everyone knew all of the good would eventually be strangled out by the lawyers and models that sought to dominate and extract for revenue control.
Re: The decline and fall of Java on the desktop
#34Eh Java never made it to the desktop. Weird.
I kinda liked developing Java Swing app but I never saw Swing apps as something very common.
On the other hand Java and the JVM "not on the desktop" kinda made it everywhere.
Re: The decline and fall of Java on the desktop
#35Earlier quoted context omitted.
> native-looking-and-feeling apps Who are you kidding? > (with some care) No. Even if you were to give it more care than required to rewrite the GUI natively in each major platform, you still wouldn't be close. Look, I get it, there are plenty of applications where a bit of clunk in the GUI is beneath other things on the priority list. That's fine. But the number of java devs who think clobbering together a few nativ…
https://docs.oracle.com/javase/tutorial/uiswing/lookandfeel/...
Re: The decline and fall of Java on the desktop
#36Earlier quoted context omitted.
Interesting, I'm not aware of any Java app that truly feels or looks native. I guess that there is definitely some selection biais, but do you have any examples of native-like Java Swing apps?
It doesn't really matter. The users don't care and who the hell would want a native looking experience on windows anyway? I haven't tried my UI on a Mac recently but I doubt anyone would notice a difference. I have used Intellij IDEA on Mac recently and I appreciated the custom theme.
I would. People who use accessibility tools that work best with native controls would as well.
Re: The decline and fall of Java on the desktop
#37Earlier quoted context omitted.
I will freely admit that Java Swing remains the only GUI toolkit I've used that I actually felt comfortable using to write a GUI, rather than something that feels like having to pull out teeth to get things working in a somewhat coherent manner.
You haven't tried AppKit, WinForms, or WPF.
Re: The decline and fall of Java on the desktop
#38Successfully using JavaFX (or OpenJFX as it is now called) in a mission-critical cross-platform app with 50k+ installs. It’s not that bad really. Package size and RAM usage is a bit of an issue, as we bundle it with a jlink’ed (stripped down to what is needed, thanks to Java 9 modules) JDK. Other options like Electron or native Windows/macOS wrappers around a shared core written in C++ were discussed but ultimately d…
It's good enough to where I think that if JavaFX had come out around the same time as Swing, the Java GUI would substantially more popular. As it stands, when I tell people I'm using JavaFX, they either don't know what I'm talking about, or they'll say "isn't that just Swing? Yuck!"
Re: The decline and fall of Java on the desktop
#39Earlier quoted context omitted.
Can you explain why it's so hard? I've had a lot better luck running Java apps than Python.
Not the parent but: Java has a long tradition of reimplementing things in Java rather than relying on system libraries. Everything from OpenSSL to tzinfo to libpng has its own Java implementation, entirely separate from anything else on the system.
Re: The decline and fall of Java on the desktop
#40As a C# developer I remember the first time I developed a GUI java application. In C# you have a code-behind file with your own code and event handlers, and a "designer file" with the generated code to set-up the GUI itself. Then I used Netbeans for a Java app, and the code file contained weird sections of artificially not editable code, and event handlers were so much more complex and cumbersome - with inner classes…
Sure but for those who remember history C# was Microsoft's answer to the incredible success that Java was clearly becoming. Being years late to the party and basically creating a (back then) Windows-only copy of Java, it's quite normal that they managed to do a few things better. Regarding UI editors: back in the days IntelliJ was already amazing and allowed to hide all that boilerplate Java code. This boilerplate co…