Ballerina is quite interesting and its flexible structural typing seems to make it a great fit for solutions that weave together multiple services.
One thing that the article does not highlight is the interop story [1]. It is currently hosted on JVM, but that is supposedly intended to be an implementation detail. So unlike Kotlin explicit ffi bindings are needed. This may create some friction for early adopters, but I guess is necessary if the type system is substantially different from the java type system. This will hopefully also make ballerina applications more portable if alternative implementations emerge in future.
Comments
Ballerina is quite interesting and its flexible structural typing seems to make it a great fit for solutions that weave together multiple services.
One thing that the article does not highlight is the interop story [1]. It is currently hosted on JVM, but that is supposedly intended to be an implementation detail. So unlike Kotlin explicit ffi bindings are needed. This may create some friction for early adopters, but I guess is necessary if the type system is substantially different from the java type system. This will hopefully also make ballerina applications more portable if alternative implementations emerge in future.
[1] https://ballerina.io/learn/java-interoperability/
Ballerina team told me that in the future Ballerina will not be hosted on JVM.
They also told me that back at Kubecon in 2018 :D
https://github.com/ballerina-platform/nballerina :) This is an active project.
It's a bad choice IMO