Streams are broken, callbacks are not great to work with, errors are vague, tooling is not great, community convention is sort of there, but lacking compared to Go. That being said there are certain tasks which I would probably still use Node for, building web sites, maybe the odd API or prototype. If Node can fix some of its fundamental problems then it has good chance at remaining relevant, but the performance over usability argument doesn’t fly when another solution is both more performant and more user-friendly.
And now they're forking Node over this ?
So I'm guessing streams will still be broken and callback will still be not great to work with.
"Ignorance is the soil in which belief in miracles grows." -- Robert G. Ingersoll