Java JIT vs. Java AOT vs. Go for Small, Short-Lived Processes

Re:Java JIT vs. Java AOT vs. Go for Small, Short-Lived Proce... by ptx on Tuesday December 24, 2019 @07:32PM (#21875912)

It fell out of favor because all the Java apps people encountered in the desktop app space were slow.

[ Parent | on HN ]

Re:Java JIT vs. Java AOT vs. Go for Small, Short-Lived Proce... by jayd16 on Tuesday December 24, 2019 @10:00PM (#21876471)

I think it has much more to do with the fact that there isn't a really great desktop UI framework for Java. Electron is a slow memory hog and people tolerate that fine.

[ Parent | on HN ]

Re:Java JIT vs. Java AOT vs. Go for Small, Short-Lived Proce... by vips7L on Wednesday December 25, 2019 @11:34AM (#21879165)

JavaFX is alright. Its just not what JS/webdevs are used to.

[ Parent | on HN ]

Re:Java JIT vs. Java AOT vs. Go for Small, Short-Lived Proce... by nobleach on Wednesday December 25, 2019 @12:23PM (#21879432)

The only Java deskop app I've used that doesn't feel bloated is Charles. It _still_ has that Swing "almost looks like OSX" look to it but otherwise, it's completely usable. I use IntelliJ nearly every day, and while it's insanely powerful, it feels so incredibly bloated. I'm running on a 6th gen Thinkpad X1C (Arch Linux), a 2017 Macbook Pro (both with 16G of RAM) and a brand new Ryzen 7 with 32G of Ram. It just isn't snappy. I've always wanted to write a JavaFX app and compare it across platforms. I've seen some really nice demos.

[ Parent | on HN ]

Re:Java JIT vs. Java AOT vs. Go for Small, Short-Lived Proce... by jayd16 on Wednesday December 25, 2019 @06:33PM (#21881092)

The slowest part of IntelliJ is scanning the project. I much prefer Rider over VisualStudio though. It doesn't feel any slower to me despite being Java.

[ Parent | on HN ]