A few days ago, I read an article about Rust being faster than C now. Some perf charts in the article showed that PHP was slower than Node.js and Go being just a tiny bit faster than Node.js.
While I agree with you that you should choose the appropriate technology for your backend, if CPU loads are really a problem for your Node.js app, you probably get better results with C/C++/Rust (compared to Node.js) than with PHP/Go.
I agree with you.
I did not pick PHP over Node.js though, you might have misinterpreted that part.
The point of the article is not to say one is better than the other, but to make you rethink your choice with Node.js on CPU bound projects or features. I gave an example of something that might work better for you with Go. Rust, Erlang, C++, even Julia tends to do better on memory intensive apps than Node.js, Go was just one example, doesn't mean it's best.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A few days ago, I read an article about Rust being faster than C now. Some perf charts in the article showed that PHP was slower than Node.js and Go being just a tiny bit faster than Node.js.
While I agree with you that you should choose the appropriate technology for your backend, if CPU loads are really a problem for your Node.js app, you probably get better results with C/C++/Rust (compared to Node.js) than with PHP/Go.
I agree with you.
I did not pick PHP over Node.js though, you might have misinterpreted that part.
The point of the article is not to say one is better than the other, but to make you rethink your choice with Node.js on CPU bound projects or features. I gave an example of something that might work better for you with Go. Rust, Erlang, C++, even Julia tends to do better on memory intensive apps than Node.js, Go was just one example, doesn't mean it's best.