Originally posted by cynical
View Post
Yes, you may not be interacting with the hardware directly; but someone has had to. Too many developers overlook this JNI usage for almost every project because they just grab a binding dependency. However as soon as they need to maintain it themselves (i.e the binding has become obsolete) then they completely lack the skill and manpower to do so and the project collapses.
Based on my experience, I am personally of the opinion that writing bindings to connect Java to native libraries, is harder and more error prone than just using a native language for the whole project directly in the long run. This is not a common belief for many Java developers because they have yet to experience the joys of maintaining a binding. They usually just whine if the binding breaks and get someone else to do the hard work.
(Obviously by Java I also include VB.NET and Csharp.NET in this since they are the same technology).
Leave a comment: