And while it is too early to talk about 2025, I think interoperability will be a major theme! Interoperability with what and how? Let me know your guesses! - ThreadSky

josevalim.bsky.social • 76 days ago

And while it is too early to talk about 2025, I think interoperability will be a major theme!

Interoperability with what and how? Let me know your guesses!

Comments

brunoanken.bsky.social•74 days ago

JavaScript? To make it easier to SSR and render UI frameworks like React?

dnautics.bsky.social•74 days ago

make me guess correctly for the fourth time huh?

josevalim.bsky.social•74 days ago

:D Unfortunately I don't think we'll have benchmarks this time around (not _that_ kind of integration)

dnautics.bsky.social•73 days ago

haha I was going to guess "readthedocs/docusaurus" integration

nezteb.net•73 days ago

Too soon. 😂

dnautics.bsky.social•73 days ago

too late for me lol

tuxified.bsky.social•75 days ago

Since 2024 saw a lot of advancement in type system and ML, I guess something related? Interoperability with Erlang (types) or ML frameworks / hardware ? Like MLX for apple silicon or better torch interop ? Or perhaps interop of Elixir types and Gleam ?

aviagarwal.bsky.social•73 days ago

A generalized LiveView for front-end of choice?

kishml.bsky.social•75 days ago

Python, Erlport isn’t cutting it

jrjsmrtn.bsky.social•76 days ago

The highly anticipated return of CORBA and DCOM ! 😅

kristoff.sh•76 days ago

+1 to Python so I could use Python libraries from Elixir 🐍

cr1spsandw1ch.bsky.social•76 days ago

It’s going to be JavaScript isn’t it?

superchris.launchscout.com•74 days ago

Making pretty good progress with Webassembly component support in wasmex. This will let us integrate with python javascript go .net rust etc using a language independent type system https://github.com/tessi/wasmex

chrichton.bsky.social•74 days ago

That sounds very interesting

genserver.be•75 days ago

I'm going to say Common Lisp!

mxgrn.com•74 days ago

Web components

rvnash.me•76 days ago

LiveView and React

brendon9x.bsky.social•76 days ago

Python and/or WASM.

tcoopman.bsky.social•75 days ago

Gleam would be my wish. Wasm a guess.

bcardarella.bsky.social•75 days ago

WASM really needs to be on the shoulders of the Erlang core team IMO to be done right. There has been a small but consistent effort within the EEF to push for this but needs more voices

binaryape.bsky.social•76 days ago

Gleam?

michaelward.uk•74 days ago

Adobe Flash integration 🤞

vladimirdotk.bsky.social•76 days ago

With Go :)

andyleclair.dev•76 days ago

FULL! JVM! INTEROP!

hauleth.dev•75 days ago

There is Jinterface already

andyleclair.dev•75 days ago

Should've said something sillier!

andyleclair.dev•75 days ago

I am aware, my post is what some would refer to as a "joke"

cmnstmntmn.com•19 days ago

integrate MCP protocol in the language

milad.rastian.me•74 days ago

Chatgpt's guess:
1.WASAM
2. AI/ML libraries
3. Cross-beam language collaboration (unified tool/enhance debugging ...)
4. Enhance Distributed systems interoperability

josevalim.bsky.social•74 days ago

I'd say one of them is right. :)

hauleth.dev•74 days ago

I would love to see better interoperability with external processes in BEAM (ports are very constrained). That would reduce need for external libraries like Porcelain, Erlexec, etc. I was working on something like that (called sport - super ports) that would use posix_spawn and all goodies there.

hauleth.dev•73 days ago

Another place where I see potential for some improvements is integration with systemd and other system-level supervisors. For example currently there is no "automatic" way to reload configuration in neither Erlang nor Elixir. Integration of EPMD with systemd/launch's would also be nice thing.

hauleth.dev•73 days ago

However honestly I would rather think about a way to replace EPMD in general. Its implementation is quite unsafe if accidentally exposed to the internet, and nowadays I think it isn't that common to have multiple unrelated Erlang VMs running on the same machine in a way that public EPMD is needed.

josevalim.bsky.social•69 days ago

FWIW, it is quite easy to run without EPMD nowadays: https://hexdocs.pm/mix/Mix.Tasks.Release.html#module-epmd-less-deployment

Livebook does a lot of creative things as well to run without EPMD while allowing port forwarding, remote nodes, etc.

hauleth.dev•69 days ago

I know that it isn't hard. My goal is to be able to use something better in place of EPMD when needed. Though in "modern" containerised world running without any EPMD is probably the most useful approach.

josevalim.bsky.social•69 days ago

Yes, exactly. I am not sure we should recommend something other than EPMD when we could recommend skipping it for most cases!

hauleth.dev•74 days ago

Example feature that I was planning was to be able to pass extra FDs to the child process, which would allow out of band communication with child process (so the stdio is still available and works "normally"). Another feature (macOS-only unfortunately) was closing all non-explicitly passed FDs

djcarpenter.bsky.social•75 days ago

LLVM integrations enabling core elixir applications to cross compile natively without third party wrappers. Kind of the natural next step for compiling directly to CUDA. This is probably way off though :D

Comments

Posting Rules

Reply