Deno.is cleaelt the better choice. I just hope that the community adopts it so that we can use in production
The community already adopted it.
Not quite. The node community is many times larger
That doesn't mean the community hasn't adopted it. What is your definition of community?
Stackoverflow questions, youtube videos, articles, etc
What is required is community parity, so everything node supports you want node to support as well, for example a Gulp alternative on deno.
But videos and stackoverflow questions on the core packages such as io and event system are necessary
Yeah, they are nesscarry but that isn't what people mean when they say they want community support, what they mean is that they want community parity between node and deno.
There's definitely room for growth in regards to spreading more awareness about the benefits of Deno!
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Deno.is cleaelt the better choice. I just hope that the community adopts it so that we can use in production
The community already adopted it.
Not quite. The node community is many times larger
That doesn't mean the community hasn't adopted it. What is your definition of community?
Stackoverflow questions, youtube videos, articles, etc
What is required is community parity, so everything node supports you want node to support as well, for example a Gulp alternative on deno.
But videos and stackoverflow questions on the core packages such as io and event system are necessary
Yeah, they are nesscarry but that isn't what people mean when they say they want community support, what they mean is that they want community parity between node and deno.
There's definitely room for growth in regards to spreading more awareness about the benefits of Deno!