News for hackers. Stuff that matters.
Re:600k concurrent websocket connections on AWS using Node.j... by anildigital on Friday October 11, 2019 @09:52AM (#21224341)
This is a very typical diplomatic answer to stick with old, known programming languages.
Re:600k concurrent websocket connections on AWS using Node.j... by arcturus17 on Friday October 11, 2019 @10:05AM (#21224468)
Maybe because a lot of the time it's good advice?
Re:600k concurrent websocket connections on AWS using Node.j... by SketchySeaBeast on Friday October 11, 2019 @11:10AM (#21225108)
Often case that isn't the wrong way to go. Newer doesn't mean better, and there's always trade-offs to consider. "It's newer" by itself really shouldn't be much of a consideration.
Re:600k concurrent websocket connections on AWS using Node.j... by nevertoolate on Friday October 11, 2019 @11:50AM (#21225517)
Erlang is older, more suitable, more stable and less well known. Nobody mentioned that it is better because newer.
Re:600k concurrent websocket connections on AWS using Node.j... by SketchySeaBeast on Friday October 11, 2019 @12:02PM (#21225629)
No, but the person I'm responding to is implying that using old, known languages is somehow a bad thing.
Re:600k concurrent websocket connections on AWS using Node.j... by verttii on Friday October 11, 2019 @11:52AM (#21225542)
But in this concrete case his point is valid, I'd likewise expect Erlang's BEAM to outperform node.js in concurrency any day of the week. Elixir being new is fairly irrelevant because it compiles down to the same erlang BYTE CODE. Erlang is 30 years old.