I think your claim, that the Deno community is in some way "lessen[ing] itself" with this change, requires more explication than you've given it, not least beca

I think your claim, that the Deno community is in some way "lessen[ing] itself" with this change, requires more explication than you've given it, not least because it's far from clear that providing a relatively straightforward onramp for existing projects and teams from Node to Deno will have any such effect.