News for hackers. Stuff that matters.

A comment on How Swift achieved dynamic linking where Rust couldn't (2019). Parent comment

Re:How Swift achieved dynamic linking where Rust couldn't (2... by pjmlp on Saturday February 20, 2021 @03:09PM (#26207454)
And you are forced to run multiple processes with OS IPC, as means for application extensions, which uses a lot of more CPU resources to get going.
[ Parent | on HN ]
Re:How Swift achieved dynamic linking where Rust couldn't (2... by zozbot234 on Saturday February 20, 2021 @04:05PM (#26207962)
But then you can simply deploy these multiple processes on separate machines and connect them via a network, and you basically get microservices!
[ Parent | on HN ]
Re:How Swift achieved dynamic linking where Rust couldn't (2... by pjmlp on Saturday February 20, 2021 @04:12PM (#26208033)
Only when they make use of IPC APIs that allows for that.

And even then good luck getting everything to work without issues.

Ah the wonders of having a language server microservice running across the network, or a image conversion plugin or audio DAW.

[ Parent | on HN ]