JNA provides Java programs easy access to native shared libraries (DLLs on Windows) without writing anything but Java code—no JNI or native code is required. This functionality is comparable to Windows' Platform/Invoke and Python's ctypes. Access is dynamic at runtime without code generation. JNA allows you to call directly into native functions using natural Java method invocation. The Java call looks just like it does in native code. Most calls require no special handling or configuration; no boilerplate or generated code is required. The JNA library uses a small native library stub to dynamically invoke native code. The developer uses a Java interface to describe functions and structures in the target native library. This makes it quite easy to take advantage of native platform features without incurring the high overhead of configuring and building JNI code for multiple platforms. While some attention is paid to performance, correctness and ease of use take priority.
Estou me acabando de tanto estudar Android com Kotlin. Sim, porque já utilizo Kotlin nos backends que desenvolvo, nos Spring Boots da vida. Agora ouço todo esse burburinho em torno do Flutter, para desenvolvimento multiplataforma Android e iOS. Fala sério! Estou atrás de leituras agora: qual as vantagens, por que o Dart, por que, por queeeeeee? Num Hello World que fiz aqui, a velocidade do Hot Reload do Android Studio no meu celular foi impressionante, quase instantâneo... Este são alguns textos que sites que acessei até agora: Should Google have chosen Kotlin for Flutter instead of Dart? - é uma pergunta lançada com Reddit, com várias respostas legais Flutter doesn’t need Kotlin (or anything else) - hummm, convincente Why Flutter Uses Dart - muuuuito convincente! Agora já quero testar Dart com bem mais atenção.
Comentários