Coding native modules using N-API sucks, coding native modules on Rust for Deno has been a breeze. Enforcing typescript is the difference between editors like VS Code being gods or being colored note taking apps.
The thing I like less about Deno is the remote imports, having a (popular) centralized package manager is the only reason Node has become what it's currently today (maybe github with their packages will be a light on Deno, idk yet).
It's not only features, top level await is ridiculously small compared to first-class typescript support. I can code a babel plugin that solve my remote imports in an afternoon but I can't make typescript development in Node more streamlined (at least not in the level Deno is attempting to).
Is first class TypeScript support that important? It still internally compiles to Javascript, though. Also, you can create tsconfig.json and add additional options.
However, among the most important, I think it is security, and web browser like modules (i.e. ditching commonjs).
Anything that lived long enough will suffer from backward compat.
I am still half hearted about not supporting gyp, relying only on web assembly.
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.
Coding native modules using N-API sucks, coding native modules on Rust for Deno has been a breeze. Enforcing typescript is the difference between editors like VS Code being gods or being colored note taking apps.
The thing I like less about Deno is the remote imports, having a (popular) centralized package manager is the only reason Node has become what it's currently today (maybe github with their packages will be a light on Deno, idk yet).
It's not only features, top level await is ridiculously small compared to first-class typescript support. I can code a babel plugin that solve my remote imports in an afternoon but I can't make typescript development in Node more streamlined (at least not in the level Deno is attempting to).
Is first class TypeScript support that important? It still internally compiles to Javascript, though. Also, you can create tsconfig.json and add additional options.
However, among the most important, I think it is security, and web browser like modules (i.e. ditching commonjs).
Anything that lived long enough will suffer from backward compat.
I am still half hearted about not supporting gyp, relying only on web assembly.