4 ms·
https://github.com/denoland/deno/discussions/11771 https://github.com/denoland/deno/discussions/11771 > NodeJS compatibility, what is our high-level strategy,
by up6w6 5y ago
https://github.com/denoland/deno/discussions/11771 https://github.com/denoland/deno/discussions/11771
> NodeJS compatibility, what is our high-level strategy, goals, next steps?
> Do we see Node and Deno co-existing, or do we want to think of Node as "legacy"? (Note, there was no clear decision on this question, it was just a conversation)
> If we could say "you can run your Express server under Deno faster than Node" would that encourage adoption? No clear answer
I really wish they go for a better compatibility with Node and sell themselves as a replacement that is strictly better.
- Mikeb85 5y agoNode is from the days before ES6 and uses a different API. Should just kill it and start fresh. Deno conforms to modern JS standards and is much more pleasant to use in pretty much every way.
- FinalBriefing 5y agoI agree that that's the direction of the future. I wouldn't start a new, important project with Deno just yet. It's still the early days.
- mcguire 5y agoYeah, things like Oracle drivers might be nice.
- galaxyLogic 5y agoNode.js adds new-style APIs all the time. The File-system API now has an async/await version which is a joy to use. When you load a library you can load a newer version or an older one. It's up to you. You can use both.
- justshowpost 5y agoChoose one: 1. Same. 2. Better. You can't have both. Since getting better involves change, which is the opposite of staying the same.