3 ms·
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 applic
by vbsteven 6y ago
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.
- smarx007 6y agoNot 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.
- chrisseaton 6y ago> 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.
- shock 6y agohttps://en.m.wikipedia.org/wiki/Java_Native_Interface https://en.m.wikipedia.org/wiki/Java_Native_Interface
- abollaert 6y ago... 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.
- deleted 6y ago[deleted]
- chrisseaton 6y agoI 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?