[staticassertion]

> FYI: If you're primarily IO-heavy, the GC pauses aren't going to be a big deal. Something like NodeJS (or Async .Net) will have great performance; even with garbage collection. (IO-heavy is the specific use case that NodeJS was designed to handle.)

This just isn't true. Node is pretty terrible even at IO heavy workloads, especially if you have servers with many cores. Any benchmark will confirm this.

[ithrow]

Is not Java or Go but surely beats the pants out of Ruby/Python, and then, Ruby/Python has been wildly successful for lots apps/companies.

[staticassertion]

Of course. It's also better than solving problems with pen and paper.

[hu3]

Their point is that GC is fine. Your're focusing on one of the suggestions: nodejs.

But .NET or Go are very fast for typical I/O bound workloads.

[staticassertion]

Yes, that's why I quoted one specific part and responded to that specific part.

[hu3]

No you included the GC part too:

> FYI: If you're primarily IO-heavy, the GC pauses aren't going to be a big deal.

To further my point: .NET and Java are amazing when it comes to performance for most cases. You get a mature ecosystem, large developer pool, fast runtime and all the comfort that GC offers.

I'd argue that choosing Rust for most startups is outright irresponsible.

[staticassertion]

Yeah fair, in my mind I was just responding to the bit about node, but whatever.

> I'd argue that choosing Rust for most startups is outright irresponsible.

I feel the opposite and I run a startup using Rust. If I could go back I'd use Rust in more places, not fewer.

[hu3]

Rust, Python and Go. Props to you for being sensible with technology choice.

https://github.com/grapl-security/grapl

https://github.com/grapl-security/pulumi-hcp

Whish you guys success.

[staticassertion]

Much appreciated

[collaborative]

Not to be a pain but Node has its place in distributed, single-core servers