On: Graphics for JVM

[smarx007]

> Like any other JVM library, it’s cross-platform. It runs on Windows, Linux and macOS. It’s as simple to use as adding a JAR file.

Well, not exactly. https://github.com/JetBrains/skija/ is 30% C++ and of course requires native builds: https://packages.jetbrains.team/maven/p/skija/maven/org/jetb.... If you are lucky, Maven simply hides it from you.

UPD: no, it doesn't hide it. See https://github.com/JetBrains/skiko/blob/master/skiko/build.g... and search for 'lin'/'mac'/'win' and see for yourself.

UPD2:

  @-moz-document domain("tonsky.me") {
  body {
      /* surovyi background color off */
      background-image: none;
      background-color: hsl(0, 0%, 85.9%);
  }
  }

[vbsteven → smarx007]

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.

[chrisseaton → vbsteven]

> 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 → chrisseaton]

https://en.m.wikipedia.org/wiki/Java_Native_Interface

[chrisseaton → shock]

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?

[abollaert → shock]

... 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.

[smarx007 → vbsteven]

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.