News for hackers. Stuff that matters.
Re:Graphics for JVM by vbsteven on Tuesday November 17, 2020 @06:32AM (#25122522)
Is this a problem? We're always going to need native blobs to interface with the OS. The JVM can package these native libraries within the jar so for the application developer it is indeed as simple as adding the jar file to your project.
Re:Graphics for JVM by chrisseaton on Tuesday November 17, 2020 @06:42AM (#25122598)
> We're always going to need native blobs to interface with the OS.

Ideally we won't when the JVM gets an FFI built-in.

Re:Graphics for JVM by shock on Tuesday November 17, 2020 @07:33AM (#25122996)
Re:Graphics for JVM by chrisseaton on Tuesday November 17, 2020 @08:24AM (#25123430)
I think you're possibly confused about what JNI is or what the discussion is about.

JNI needs binary blobs. The new FFI won't. So we will not need binary bobs when we get the new FFI.

See?

Re:Graphics for JVM by abollaert on Tuesday November 17, 2020 @07:49AM (#25123108)
... which is why we want to use FFI instead ;-) Now you already can using JNA though. JNI still requires you to write native code and compile it for your target platform, FFI eliminates that need.
Re:Graphics for JVM by smarx007 on Tuesday November 17, 2020 @06:34AM (#25122537)
Not at all! Desktop apps require platform-specific executables and installers so this is unavoidable. But the author made it sound like a piece of cake for developers used to making JAX-RS services.