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.
HN user
mjs2600
my public key: https://keybase.io/mjs2600; my proof: https://keybase.io/mjs2600/sigs/6nFFXHYaF-_2tjWlZSlMfUMXhZlyhan8wrpyJsW2O0s
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.
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...
That's the macros. Phoenix's routing is an awesome example of the power of Elixir macros. It leverages the BEAMs pattern matching capabilities to do the routing, but the syntax is very clear and concise.
I agree, but as a user you don't have any control over that. Https Everywhere is a solution to the immediate problem.
It's already in melpa.
I have a lot less issues with all of my utilities combined than I have with comcast...
Knoxville is a Comcast test market, so we get data caps. You can buy a faster connection, it just means you hit the cap faster. Just a heads up on what Comcast is planning on doing to you next...
If you name it readme.org, then github will render it as html.
Elixir has Lisp-style macros with a Ruby syntax. It's not quite as close to the AST as a Lisp, but I think the trade off hits a sweet spot. For example:
quote do
1 + 1
end
returns: {:+, [context: Elixir, import: Kernel], [1, 1]}
which, if you squint at it, starts to look a little Lispy.I think you're thinking of LFE, which is another lisp on the BEAM.