home.social

#jep424 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #jep424, aggregated by home.social.

  1. Anyone working with #ProjectPanama in #IntelliJIDEA knows whether there is an project-wide option to set some `—enable-native-access` flags? I.e. not in each run target individually?

    Every time I run a unit test, I need to set these manually. Maybe the IDE can adapt flags from surefire or failsafe config in the pom.xml?

    #java #jep424 #jep434

  2. Anyone working with #ProjectPanama in #IntelliJIDEA knows whether there is an project-wide option to set some `—enable-native-access` flags? I.e. not in each run target individually?

    Every time I run a unit test, I need to set these manually. Maybe the IDE can adapt flags from surefire or failsafe config in the pom.xml?

    #java #jep424 #jep434

  3. Anyone working with #ProjectPanama in #IntelliJIDEA knows whether there is an project-wide option to set some `—enable-native-access` flags? I.e. not in each run target individually?

    Every time I run a unit test, I need to set these manually. Maybe the IDE can adapt flags from surefire or failsafe config in the pom.xml?

    #java #jep424 #jep434

  4. Anyone working with #ProjectPanama in #IntelliJIDEA knows whether there is an project-wide option to set some `—enable-native-access` flags? I.e. not in each run target individually?

    Every time I run a unit test, I need to set these manually. Maybe the IDE can adapt flags from surefire or failsafe config in the pom.xml?

    #java #jep424 #jep434

  5. Anyone working with #ProjectPanama in #IntelliJIDEA knows whether there is an project-wide option to set some `—enable-native-access` flags? I.e. not in each run target individually?

    Every time I run a unit test, I need to set these manually. Maybe the IDE can adapt flags from surefire or failsafe config in the pom.xml?

    #java #jep424 #jep434

  6. As promised, here is a small update on the #libFUSE bindings for #Java using #jep424 I'm currently working on for @cryptomator:

    In an upcoming release we'll change two (or three) things that will boost (not just) r/w performance:

    1. Switch from AES-CTR + HMAC to AES-GCM (eliminating expensive sha256 computations)
    2. switch from fuse-jnr to jFUSE
    3. potentially switching from macFUSE to tuse-t on macOS

    I did some benchmarks on my Mac showing the relative performance increments of each change: