On: Server-Side I/O Performance: Node vs. PHP vs. Java...

[pjmlp]

So he acknowledges that has not benchmarked the best options for Java and then selects Go as a winner, what a joke.

[randomdata → pjmlp]

Reminds me of a "real world" web language shootout I once read, which included accessing a database populated with a large dataset.

The author used a query along the lines of:

    SELECT * FROM table ORDER BY RAND() LIMIT 1

Except for the language they wanted to win, which was basically written like:

    SELECT * FROM table WHERE id = RAND()

Which, of course, resulted in it their favorite being the clear winner.

[didibus → pjmlp]

Same with Php, using really old versions of it. This is a waste of time article, nothing is learned from it appart the bias of the author.

[frugalmail → didibus]

Ummmm when you care about I/O performance and your building anything of substance (something more than what nginx can do on it's own) why would you choose PHP? The security, fragility and un-maintainability alone are enough reasons to avoid it.

[didibus → frugalmail]

I'm not promoting php's use, just pointing out how benchmarking against a years old of anything is pretty useless. Which is another indicator the article was of low value and interest, providing no real, meaningful insight into those different languages.