I think he's alluding to the stuff that comes after the language is released, not the language design/architecture itself. Node is not a language, so his comment probably implies that he's referring to the design choices of build system, development cycle (of tools, libraries and frameworks), and things like dependency management.

That's not my opinion, but just what I understood his comment to be about (personally I prefer the npm approach any day over Maven).