3 ms·
As opposed to .NET’s mostly portable library ecosystem?
by GiorgioG 2y ago
As opposed to .NET’s mostly portable library ecosystem?
- codr7 2y agoDefinitely not as mature and portable from my experience.
- metaltyphoon 2y agoWell… the moment you have to do FFI in Java is when you give up. It’s straight up the worst I’ve seen from all higher level languages. I rather do CGO than use JNI. Its actually less bad when using Rust but still bad.
- za3faran 2y agoThis is supposed to replace JNI from what I gather: https://openjdk.org/jeps/442 https://openjdk.org/jeps/442
- vips7L 2y agoJava is my go to for everything. In my entire career I’ve never had to use FFI.
- metaltyphoon 2y agoInteresting, from 3 different jobs, all of them needed FFI. The first one was using C#. The second was Swift and Java (android). The current one is Java, NodeJS, C#, Python, Go. This tends to happen when you want to write common shared libraries that are business critical and want one implementation only or when the library exist but in another language.
- codr7 2y agoNever did FFI for exactly the stated reason; there are portable, mature libraries for almost anything.
- metaltyphoon 2y agoSo from your experience which part, specifically, wasn't portable?