I was just contesting the assertion of "switching in droves" by parent post. Find me a case of a nodejs community "switching in droves" to deno if you know some, or even a high impact project in nodejs currently switching to deno, if your intention is to assert that parent's assertion is correct.

My thoughts are that atm there is no reason to switch your project(s) to it and that, for the features Deno offers right now, it was indeed severely overhyped

They're pointing out that anecdotally, Deno seems to be a non-player right now. Which is pretty spot on: it's still very new, and hasn't found a critical application yet (e.g. would Node have taken off the way it did without Express? Probably not). So right now, it's an enthusiast's plaything, even if the architectural principles are much cleaner (wrt modern JS) than Node can ever become - without a rewrite so drastic it'll split the Node community like Perl 5/6 or Python 2/3, at least.