4 ms·

Non of what you just said was an actual argument against node.js though. All you said was "Well, we don't like it" Why don't you like it? What's wrong with it?

• jjnoakes 11y ago
  > All you said was "Well, we don't like it" That's not what I see.
• otterley 11y ago
  It's not about Node per se; it's about JavaScript. System telemetry collectors don't benefit much from languages built around event loops. Many of us already know C, Bourne Shell and Python and probably another scripting language and all of those can get telemetry data off systems and into an event bus or metrics aggregator quickly enough. Adding JavaScript adds complexity without giving us significant new functionality. Now the data collector (gathering metrics from many senders for aggregation and storage) is a different story. I've seen them written in JavaScript but the 64-bit counter difficulties would rule it out for me were I to implement one again.
• crdoconnor 11y ago
  It's a weakly typed language and it exhibits all kinds of bizarre not-very-well-thought out behaviors. c.f. the disaster with npm a few days ago. These problems are particularly pernicious for large scale apps - which this isn't, currently, but probably aspires to be one day. Any strongly typed language would be better (python, go, ruby, etc.).
  • geofft 11y ago
    Can you explain how the npm incident is related to typing? I am an advocate of strong typing and love seeing it be the answer to all sorts of problems (e.g. concurrency), but I'm not understanding the connection here.
    • crdoconnor 11y ago
      That wasn't related to js's weak typing and I didn't say that it was, but it's indicative of the types of other problems that will occur.