2 ms·
I can't help but recoil from a "hello world" that pulls in an entire container ship of dependencies. Especially that we already have a perfectly good, battle-h
by btbuildem 5y ago
I can't help but recoil from a "hello world" that pulls in an entire container ship of dependencies.
Especially that we already have a perfectly good, battle-hardened, and relatively lightweight implementation of Actor model with Erlang / Elixir.
- capableweb 5y ago> I can't help but recoil from a "hello world" that pulls in an entire container ship of dependencies. Where do you see the list of dependencies? Seems to me to be the ones defined at https://github.com/orbit/orbit/blob/233956001f1206ccbfde72efb0eab8479761951e/build.gradle.kts#L14-L35 https://github.com/orbit/orbit/blob/233956001f1206ccbfde72ef..., is that correct? Doesn't look like "an entire container ship" but maybe the NPM madness have ruined me. > Especially that we already have a perfectly good, battle-hardened, and relatively lightweight implementation of Actor model with Erlang / Elixir. Yeah, if you're already using Erland or Elixir, why don't you go with that instead? This seems to be for the JVM, so one could assume that the ones who want to use this, is already invested heavily in the JVM ecosystem (which as far as I know, EA is when it comes to backend servers).