JVM developers find native library integration tedious
Java, Kotlin, and Clojure developers say that calling native libraries can be difficult, bindings may not feel idiomatic or complete, and cross-platform wrappers take tedious integration work. Packaging adds another chore: one developer describes manually excluding unused native libraries to avoid bloated uberjars. The signals point to related parts of JVM-native integration, but do not establish how common the problem is beyond these reports.
For JVM developers integrating native libraries. Mentioned from Dec 2023 to May 2024 on Hacker News.
4 different people described this problem in 3 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.0/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Native calls are rare in Java because they're such a pain. If it wasn't so hard to do native calls in Java, it would be common even for non-experts to make use of non-Java libraries
cesarb on Hacker NewsMay 2024It'd be nice to see some good language bindings that feel right for java
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks