---
title: "Comment by Matthew Marcus on \"Performance Testing a Real-World Back-End: NodeJS vs Go\" | Hashnode"
description: "Cool story bro. Now, instead of posting a perceived \"dunk\" on a single-threaded process technology, by doing a comparison w/ a multi-threaded process technology"
url: "https://hashnode.com/posts/performance-testing-a-real-world-back-end-nodejs-vs-go/668a70fc84f03495e69710da/comment/6841c76302aa0964d0b5f927"
---

[Discussion](https://hashnode.com/posts/performance-testing-a-real-world-back-end-nodejs-vs-go/668a70fc84f03495e69710da)

Comment [Performance Testing a Real-World Back-End: NodeJS vs Go](https://hashnode.com/posts/performance-testing-a-real-world-back-end-nodejs-vs-go/668a70fc84f03495e69710da)

[Matthew Marcus](https://hashnode.com/@troop4christ)

[Jun 5, 2025](https://hashnode.com/posts/performance-testing-a-real-world-back-end-nodejs-vs-go/668a70fc84f03495e69710da/comment/6841c76302aa0964d0b5f927)

Cool story bro.

Now, instead of posting a perceived "dunk" on a _single-threaded_ process technology, by doing a comparison w/ a multi-threaded process technology, go and perform and actually _relevant_ comparison w/ an API implementing node-cluster or worker-threads.

Choosing to _not_ use a performance-boosting feature of a technology, doesn't make that given tech inherently "slower" than the other tech that _is_ using that feature. It's just ignorant.