News for hackers. Stuff that matters.
Re:How Four Native Developers Wrote an Electron App by flukus on Thursday May 18, 2017 @11:55PM (#14372910)
Java on the desktop died because it didn't provide a native enough look and feel and it performed too slowly. Now we just don't care about look and feel and pretend every user has 16GB of RAM like the developer machines do.
Re:How Four Native Developers Wrote an Electron App by brandonmenc on Friday May 19, 2017 @12:09AM (#14372956)
> and pretend every user has 16GB of RAM

I currently have two separate JetBrains IDEs each with multiple projects opened on my 8 GB MacBook Air. Doesn't seem to be a problem.

Re:How Four Native Developers Wrote an Electron App by flukus on Friday May 19, 2017 @12:26AM (#14373024)
I was talking more historically. Java was slow and fell out of favor at a time when the average desktop had 16MB of RAM (and many had less). It never recovered from that perception and was pretty much confined to server side tasks.

Now developers are working on electron apps and the average machine with 2GB makes an electron app today feel like a java one from 20 years ago.

Re:How Four Native Developers Wrote an Electron App by relyks on Friday May 19, 2017 @12:00AM (#14372929)
JavaFX is actually pretty good and the performance is much better than Electron.
Re:How Four Native Developers Wrote an Electron App by pjmlp on Friday May 19, 2017 @12:28AM (#14373031)
Java on the desktop died because most developers were too lazy to learn how to use Swing properly, while writing everything on the UI thread.
Re:How Four Native Developers Wrote an Electron App by pssdbt on Friday May 19, 2017 @12:48AM (#14373094)
Example of a properly done Swing app? Not trolling, genuinely curious to see what that looks like (code + result). I also assumed it was because they perform terribly and look non-native.
Re:How Four Native Developers Wrote an Electron App by pjmlp on Friday May 19, 2017 @02:15AM (#14373370)
Bitwig Studio, https://www.bitwig.com/en/bitwig-studio.html

Booksmart. http://www.blurb.com/booksmart

Ultramixer, http://www.ultramixer.com

jAlbum, https://jalbum.net/en/

VRL Studio, http://vrl-studio.mihosoft.eu/

Centigrade UI Components, http://www.centigrade.de/en/products/bizlaf-stock-look-and-f...

Synthetica UI Components, http://www.javasoft.de/synthetica/

JGoodies UI Components, http://www.jgoodies.com/products/smart-client/

SQL Developer from Oracle is also quite ok.

The sample applications developed on the "Filthy Rich Clients" book, http://filthyrichclients.org/

You can watch the related JavaONE 2008 session at

http://www.oracle.com/technetwork/java/j1sessn-jsp-155597.ht...

Oh and MATLAB is also a Swing application.

Re:How Four Native Developers Wrote an Electron App by riffraff on Friday May 19, 2017 @01:19AM (#14373209)
The IntelliJ stuff is Swing IIRC, but not open source.

jEdit, IIRC, was often mentioned as a properly written java GUI app, I think it's Swing, but I might be wrong.

EDIT: IDEA code is apparently open https://github.com/JetBrains/intellij-community

Re:How Four Native Developers Wrote an Electron App by flukus on Friday May 19, 2017 @12:45AM (#14373086)
I don't buy that excuse, it never affected winforms or vb take-up that often had the same issue.
Re:How Four Native Developers Wrote an Electron App by pjmlp on Friday May 19, 2017 @01:07AM (#14373160)
First of all you are talking about OS SDKs, first class platform languages designed by the OS owners.

Second anyone that bothered reading Filthy Rich Clients book should be capable of doing a WinForms like experience.

What I conceed is that Swing has the wrong defaults and requires more UI design skills from devs than Forms does.

Re:How Four Native Developers Wrote an Electron App by pvg on Friday May 19, 2017 @12:11AM (#14372961)
All the IntelliJ environments are Java based and seem reasonably well-liked. So it seems alive and well, in its niche.
Re:How Four Native Developers Wrote an Electron App by imron on Friday May 19, 2017 @11:42AM (#14376752)
> Java on the desktop died because it didn't provide a native enough look and feel and it performed too slowly

Not to mention end users needed to download and update hefty runtimes in order to run the software.

Re:How Four Native Developers Wrote an Electron App by pyrophane on Friday May 19, 2017 @12:55AM (#14373122)
Has the latter problem been solved? Jvm startup times still seem like an issue to me.
Re:How Four Native Developers Wrote an Electron App by niftich on Friday May 19, 2017 @01:20AM (#14373212)
The JVM isn't actually slow to start [1] (albeit it does start about 3x-4x slower than python, ruby, or node) [2]. Most of the slow startup in a JVM-based application is in classloading [3] or waiting for your chosen framework to initialize [4] before the control is handed to your custom code.

[1] https://purelyfunctional.tv/article/the-legend-of-long-jvm-s... [2] https://dev.clojure.org/display/design/Improving+Clojure+Sta... [3] http://blog.ndk.io/clojure-bootstrapping.html [4] https://jkutner.github.io/2015/12/01/java-boot-time.html