I found this[1] section in the documentation on interoperability within the JVM. It looks fairly straightforward to work with. I'm not sure about FFI more generally.

[1] https://doc.flix.dev/interoperability/

Enforcing and incentivizing collaboration also seems like a good argument for licensing open source projects with the AGPL. It prevents people who are not willing to contribute things made using your software back to open source from using it.

Yep, it works really well for that. https://poetry.eustace.io/docs/cli/#publish

I don't think he's getting enough credit for this.

C can compile to WASM, but I have no clue about external tools like BLAS. I'd assume that things like Numpy are able to work without tools like BLAS, but you might also be able to compile the essential ones to WASM as well.

NumPy can work without libraries like BLAS or LAPACK, but it will be sloooooooooow. There are C versions of those libraries however, maybe they are using those?

Yes. It uses the C implementations of BLAS and LAPACK that ship in the Numpy source tree.

It definitely seems like it does https://docs.racket-lang.org/guide/parallelism.html

The focus on improving reinforcement learning is really exciting. It's the area of machine learning that seems to have the most untapped potential.

I reloaded and it worked.

I came back to it recently after a year and a half long break and it has improved dramatically. It's starting to feel like something I'd be comfortable using in production.

It works, eventually...