[jeroenhd]

I don't see the relevancy of rust here, but you're right that at this point any language that compiles directly to machine code will blow any javascript tool out of the water any time.

Of course, perf is only one reason to use a tool, I expect javascript based tooling to stick around for much longer because developers are used to them now. And, of course, if all you know is frontend, everything starts to look like a javascript job.

[serverholic]

I'd prefer my tools to use languages that are compiled + memory safe. Basically that just leaves rust or go.

But rust also has other features that can help prevent bugs regarding concurrency and more. So rust is a feature in my book and not just an implementation detail.

[jeroenhd]

I agree, but there's still plenty of alternatives. Pre-compiling languages like C# and Java will already provide a speed bonus, and with stuff like GraalVM's native images and Kotlin native you can squeeze even more performance out of these GC'd languages.

At this point in time, improvement comes from "anything faster than node". Hell, you might even manage to get a performance benefit out of PHP with the way things are right now.

[mssundaram]

[redacted]

[serverholic]

Is go not compiled and memory safe?