6 ms·

Realtime? In nodejs? It must be a webscale realtime, or at least reactive realtime..

• hackerboos 10y ago
  If you're willing to put the work in to load balance then it can probably scale quite well. I'm always baffled why people choose JS over Erlang/Elixir which is designed to do this and comes with the tools/libs required to scale.
  • elcct 10y ago
    Exactly word "probably" is a deal breaker in this case. I am also curious how someone was thinking JS will be a good idea for such project. But hey, there are people building cars out of plastic bottles...
    • wolframhempel 10y ago
      We are working with Alex,creator of µWebSockets (https://github.com/uWebSockets/uWebSockets https://github.com/uWebSockets/uWebSockets) on moving all connectivity and networking aspects to low level C
      • stemuk 10y ago
        Would this mean you are getting rid of engine.io as the base, or is this just meant to be a general addition?
      • wolframhempel 10y ago
        yes, that's one major aspect of it. engine.io adds is own protocol and isn't exactly the most performance tuned library
        • stemuk 10y ago
          Is there some data available on which factor the perfomance benefitted from this change (like some benchmark results)?
        • wolframhempel 10y ago
          Sorry, it doesn't let me reply for some reason :-( Development is in progress, there will be figures soon
          • stemuk 10y ago
            It seems like you have to wait some seconds for the server to process the comment, if you refresh it should let you comment again. Anyway, looking forward to the data release, through a blog post I suppose?
            • wyldfire 10y ago
              That feature of HN is by design. It's there to force you to think about your replies instead of engage in knee-jerk flamewars. :)