5 ms·
And likely will have similar issues in five years as node has now. Node was once thought to be the cleaner alternative that had a lot of these features built i
by drannex 6y ago
And likely will have similar issues in five years as node has now.
Node was once thought to be the cleaner alternative that had a lot of these features built in, it was the supposed savior of Javascript, and now look at where we are.
- ficklepickle 6y agoI think that is an unnecessarily negative view. By that logic, nobody should do anything because it will probably suck someday.
- drannex 6y agoI do believe constant iteration is better, but Javascript has many problems at its very core, and many Node developers transitioning to Deno are going to create and write solutions that are more akin to their comfort in Node. This will lend itself to reproducing similar issues as they currently have. I am primarily a javascript developer, I've written both Node and Deno projects, but I don't see the issues being solved by just rewrapping the source output.