Earlier quoted context omitted.
Excuse a quick aside -- do you know of any good examples of real non-enterprisey apps using JavaFX? Java desktop apps seem almost universally awful, but it doesn't seem like it has to be that way. I'd love to see some counter examples (IntelliJ's IDEs are honourable exceptions, but they're a bit of a special case).
The old LoadUI (load testing tool) was written in JavaFX, you can still see the old screenshots in the documentation: https://www.loadui.org/working-with-loadui/projects.html Also, there's LoadFX (a logging viewer) which was part of the rage post against Electron last week: https://github.com/renatoathaydes/LogFX And Gluon keeps a list of sample apps: http://gluonhq.com/developers/samples/
Show HN: Hacker News desktop application in Kotlin/Swing
81–90 of 92 posts
Re: Show HN: Hacker News desktop application in Kotlin/Swing
#82Earlier quoted context omitted.
Thanks, looks interesting. Scriptable in javascript too. I always note with irony that professionals expect to pay decent money (Bitwig is $400) for software relevant to their trade; the one exception being software pros.
Visual Studio Enterprise is $2999/year, Pro is $539. Might as well add anywhere from $400 to $1500 for the IncrediBuild license.
Re: Show HN: Hacker News desktop application in Kotlin/Swing
#83Earlier quoted context omitted.
> There's a reason Java became such a big platform for business applications and it isn't because it cared about fashion fads. There's a reason why Java completely failed on the desktop: Swing. > Which do you care more about: it works, or it looks good? Both. I care about both. And you should too. But Swing developers got used to only being able to have one. At most.
Completely failed? JetBrains' IDEs seem awfully popular, and they are all Java and Swing.
Re: Show HN: Hacker News desktop application in Kotlin/Swing
#84Earlier quoted context omitted.
Which do you care more about: it works, or it looks good? There's a reason Java became such a big platform for business applications and it isn't because it cared about fashion fads.
> There's a reason Java became such a big platform for business applications and it isn't because it cared about fashion fads. There's a reason why Java completely failed on the desktop: Swing. > Which do you care more about: it works, or it looks good? Both. I care about both. And you should too. But Swing developers got used to only being able to have one. At most.
Why? What value is looking good? There's value in a well designed responsive UX, but how it looks is completely meaningless to me because it doesn't help me get shit done.
Re: Show HN: Hacker News desktop application in Kotlin/Swing
#85Earlier quoted context omitted.
Visual Studio Enterprise is $2999/year, Pro is $539. Might as well add anywhere from $400 to $1500 for the IncrediBuild license.
It's really the expectations I was commenting on more than the pricing. I have heard devs on 100k plus whinge about $80 for a professional programmers editor, and rule out IntelliJ IDEs from their consideration because they're not 'free'.
Re: Show HN: Hacker News desktop application in Kotlin/Swing
#86The other day there was a post recommending the use of JavaFX. I would really like to see a non-trivial app built on JavaFX in Kotlin, with the following properties: - Does not look ugly. - Is not composed of _merely_ OEM widgets. But includes custom elements, like one would normally see on websites (and by extension, Electron apps). - Is lightweight and response, not just in terms of CPU and RAM, but in terms of use…
Not sure it meets all 3 requirements, but last time I tried I was rather impressed by the Nightcode Clojure IDE built with JavaFX: https://sekao.net/nightcode/
Re: Show HN: Hacker News desktop application in Kotlin/Swing
#87Ask HN on Show HN: Why is Swing UI still so Ugly ? 2 Decades since it's introduction in 1997 ( I remember being forced to use it in a trading OMS application in 2002), Swing UI looks frozen in time, ugly as ever.
Because most developers don't bother to read Sun tutorials and books like "Filthy Rich Clients".
Re: Show HN: Hacker News desktop application in Kotlin/Swing
#88Earlier quoted context omitted.
> There's a reason Java became such a big platform for business applications and it isn't because it cared about fashion fads. There's a reason why Java completely failed on the desktop: Swing. > Which do you care more about: it works, or it looks good? Both. I care about both. And you should too. But Swing developers got used to only being able to have one. At most.
Completely failed? JetBrains' IDEs seem awfully popular, and they are all Java and Swing.
Even if you can, you can count them on one hand. Swing was a massive failure, and rightfully so, because Swing/JavaFX apps look, and more importantly, feel, like a broken mess.
In contrast, SWT/JFace apps look a lot more native and feel extremely snappy. Apps build on the Eclipse RCP are in general pretty decent looking and they enable all the native controls and functionalities of the host platform.
Re: Show HN: Hacker News desktop application in Kotlin/Swing
#89Earlier quoted context omitted.
Because Sun made the boneheaded decision (and never admitted it was dumb) to go for emulated widget controls instead of native ones. What this means is that they have had to reimplement and imitate the behavior of native controls on all platforms (realistically, Windows only) every time Microsoft came up with a new version. In contrast, IBM took the native approach with SWT / JFace, and the interfaces written with th…
The toolkit based on native widgets existed before Swing. It was called AWT.
The fact that Swing ended up being such a massive failure was in good parts due to the fact that Swing is built on top of AWT.
Re: Show HN: Hacker News desktop application in Kotlin/Swing
#90Earlier quoted context omitted.
Because most developers don't bother to read Sun tutorials and books like "Filthy Rich Clients".
"Filthy Rich Client" only shows how to do it, but it's still much, much harder than in QML (even Qt Widgets supported CSS styling) and WPF. I would say by a factor of at least 5 regarding QML and slightly less for WPF.
Not reading such books, just meant many devs were totally unaware of how to do it.