You wouldn't need to worry about library breaking OR performance if you replace node.js with asp.net core :D Sometimes choosing worse performance is not a trad

You wouldn't need to worry about library breaking OR performance if you replace node.js with asp.net core :D Sometimes choosing worse performance is not a tradeoff in favor of ease of use, sometimes the technology just has strict performance ceiling or critical deficiency that cannot be addressed.