Are you lost on your way to Reddit? Hardly a productive comment.
While mine was a bit tongue-in-cheek and apparently stung several people, it also has facts behind it. Working on many super-parallel tasks like, you know, good old web apps and APIs, have shown me that using regular threads does not scale.
There is tech out there that solves these problems and many C# and Java devs come off as grumpy curmudgeons instead of being proper techies and engaging arguments on their merit. And you seem to be another example.
Do better. The metrics and numbers are out there on the internet clearly showing that M:N parallel runtimes beat the classic threading model. That you might have chosen not to look for them is not a rebuttal by itself.
You do realize that all these are about multiplexing multiple logical threads of execution on top of few physical threads of the executor? Getting this wrong alongside the Java argument (because Java retrofitted green threads - it could not adopt async/await, pushing it away from the scenarios .NET is already good at) does show me that you neither know how modern async runtimes are implemented nor understand the meaning behind the keywords repeated in every message.
While mine was a bit tongue-in-cheek and apparently stung several people, it also has facts behind it. Working on many super-parallel tasks like, you know, good old web apps and APIs, have shown me that using regular threads does not scale.
There is tech out there that solves these problems and many C# and Java devs come off as grumpy curmudgeons instead of being proper techies and engaging arguments on their merit. And you seem to be another example.
Do better. The metrics and numbers are out there on the internet clearly showing that M:N parallel runtimes beat the classic threading model. That you might have chosen not to look for them is not a rebuttal by itself.