3 ms·

That really depends on what you're building.

• adamnemecek 7y ago
  When would erlang,jvm be preferable over actix.
  • dilatedmind 7y ago
    rust is still figuring out async, so it's not as good a fit as say go or elixir. If you are specifically making a graphql backend, idk why you would anything but node, since it has the most mature ecosystem.
    • adamnemecek 7y ago
      I mean actix just hit 1.0 and I don’t think it impacted them one bit.
      • qaq 7y ago
        The ecosystem is not really mature.
  • skosch 7y ago
    They're all wonderful, established technologies and all very capable of making concurrency relatively painless. At this stage, you should go with whatever you would be most productive in: do you already know one of the languages? If so, go with that one (always be shipping!). If not, how much do you like the syntax of each? How much do you rely on static types? How mature are the third-party libraries you're going to be relying on? I've been building software using the exact stack described in the linked article for the last three years. I don't think about my backend very much, it mostly just works. Most of the work is on the front end. Elixir/Phoenix/Absinthe have been almost completely frustration-free. I'm sure Rust and Kotlin are great too.