If that's the question you're pondering in order to decide whether or not to switch, you basically have no reason to switch yet. Stick with Node.
However, if you've gotten more and more annoyed with Node's legacy method of requiring modules (because it predates modern modules) and legacy method of dealing with asynchronous code (because it predates promises and async/await), then you already know why Deno might -once it's matured a bit, because it's super early days still- be worth your time.
However, if you've gotten more and more annoyed with Node's legacy method of requiring modules (because it predates modern modules) and legacy method of dealing with asynchronous code (because it predates promises and async/await), then you already know why Deno might -once it's matured a bit, because it's super early days still- be worth your time.