5 ms·

I wish they did not decouple JavaFX...

by java-man 8y ago

vlaaad 8y ago
Why is that? Decoupling benefits JavaFX so it can have release cycles on their own pace.
- java-man 8y ago
  Decoupling might have benefitted JavaFX, but it did not benefit me who develops professional desktop applications for a living, and it did not benefit my users. If they wanted to decouple, they first should have created a cross-platform jpackager-like tool that generates native executables for major platforms. I remember JavaFX was launched with great fanfare as a modern replacement, which it certainly might have been - a modern, efficient platform. I am afraid it will slowly decay and dissolve into oblivion to be replaced by gigabyte-size electron apps.
  - freeone3000 8y ago
    This tool is called jlink. https://docs.oracle.com/javase/9/tools/jlink.htm https://docs.oracle.com/javase/9/tools/jlink.htm
    - java-man 8y ago
      does it create a native executable?
      - freeone3000 8y ago
        It builds a directory of files which contains a .bat to launch the bundle.
        java-man 8y ago
        so it DOES NOT build a native app (jpackager does, but it's a mess: present in 8, removed in 9, coming back in 12 without cross-platform targeting). The major point of JavaFX is cross platform development. Please offer a cross-platform jpackager, and we'll be happy.
samus 8y ago
Yeah, that kinda makes it impossible to become a successor to Swing. But the situation actually got more sane because JavaFX can be included now as a Maven dependency, like any other framework.
- james_s_tayler 8y ago
  Why do people still use Maven when Gradle exists? I'll never know.
  - pjmlp 8y ago
    Because Maven doesn't require a background daemon eating 2GB of memory to be fast and IDEs can actually provide code completion and documentation while typing. Android is the only reason to have to put up with Gradle.
    - james_s_tayler 8y ago
      Fair enough. It doesn't sell me on switching back to Maven. Ram is cheap enough. With 32GB Gradle can have a couple if it wants.
      - pjmlp 8y ago
        Most dev laptops are still running with 8GB. 2GB for a cache that isn't required by alternatives for the same result just feels bad. And don't get me started into turning build scripts into full blown applications impossible to decipher what is going on without some kind of debugging process.
    - ptx 8y ago
      Gradle 5 lets you write the build scripts in Kotlin, which is supposed to address the code completion issue. (And the continuous build mode is a nice feature!) But, yes, is does use a lot of memory.
      - pjmlp 8y ago

I wish they did not decouple JavaFX...

vlaaad 8y ago

Why is that? Decoupling benefits JavaFX so it can have release cycles on their own pace.

java-man 8y ago
Decoupling might have benefitted JavaFX, but it did not benefit me who develops professional desktop applications for a living, and it did not benefit my users. If they wanted to decouple, they first should have created a cross-platform jpackager-like tool that generates native executables for major platforms. I remember JavaFX was launched with great fanfare as a modern replacement, which it certainly might have been - a modern, efficient platform. I am afraid it will slowly decay and dissolve into oblivion to be replaced by gigabyte-size electron apps.
- freeone3000 8y ago
  This tool is called jlink. https://docs.oracle.com/javase/9/tools/jlink.htm https://docs.oracle.com/javase/9/tools/jlink.htm
  - java-man 8y ago
    does it create a native executable?
    - freeone3000 8y ago
      It builds a directory of files which contains a .bat to launch the bundle.
      - java-man 8y ago
        so it DOES NOT build a native app (jpackager does, but it's a mess: present in 8, removed in 9, coming back in 12 without cross-platform targeting). The major point of JavaFX is cross platform development. Please offer a cross-platform jpackager, and we'll be happy.

samus 8y ago

Yeah, that kinda makes it impossible to become a successor to Swing. But the situation actually got more sane because JavaFX can be included now as a Maven dependency, like any other framework.

james_s_tayler 8y ago
Why do people still use Maven when Gradle exists? I'll never know.
- pjmlp 8y ago
  Because Maven doesn't require a background daemon eating 2GB of memory to be fast and IDEs can actually provide code completion and documentation while typing. Android is the only reason to have to put up with Gradle.
  - james_s_tayler 8y ago
    Fair enough. It doesn't sell me on switching back to Maven. Ram is cheap enough. With 32GB Gradle can have a couple if it wants.
    - pjmlp 8y ago
      Most dev laptops are still running with 8GB. 2GB for a cache that isn't required by alternatives for the same result just feels bad. And don't get me started into turning build scripts into full blown applications impossible to decipher what is going on without some kind of debugging process.
  - ptx 8y ago
    Gradle 5 lets you write the build scripts in Kotlin, which is supposed to address the code completion issue. (And the continuous build mode is a nice feature!) But, yes, is does use a lot of memory.
    - pjmlp 8y ago