I'm not so close enough to Node lately to know the feeling, but my sense is that it's essentially "node, but better", which wouldn't be something everyone would take so seriously if it weren't created by the creator of node.
Also, node as a thing to me was always great idea, great opportunity, not-so-great ultimate development experience or outcomes.
I also get the sense that it's good timing in terms of the maturity of TypeScript.
I'm still learning how to use Node anyway, so it makes sense that I wouldn't get it, but "Node but better" from the guy that made Node does sound pretty appealing.
Might be a dumb question, but what is this supposed to replace? What problems is this solving in the web world that's got everyone all hyped?
I'm not so close enough to Node lately to know the feeling, but my sense is that it's essentially "node, but better", which wouldn't be something everyone would take so seriously if it weren't created by the creator of node.
Also, node as a thing to me was always great idea, great opportunity, not-so-great ultimate development experience or outcomes.
I also get the sense that it's good timing in terms of the maturity of TypeScript.
I'm still learning how to use Node anyway, so it makes sense that I wouldn't get it, but "Node but better" from the guy that made Node does sound pretty appealing.
Thanks for your thoughts!
I appreciate this response after seeing this acronym/name float around here and there but had no time to figure out what deno actually was.
I know that feeling all too well 😄