I wrote some small scripts in it, I want to love it but in practice it's been quite painful, especially if the project has some browser/Node stuff in it too. My editor (vs code) does not want to understand both at the same time.
I tried to use Deno to execute tests for a ServiceWorker project (on Cloudflare Workers), it makes a lot of sense because Deno is a lot closer to a WebWorker than Node is (in terms of global API), but you run into all sorts of problems.
One glaring one is the Typescript compiler not accepting imports that end in .ts, which is a total killer for Deno. I need to use the typescript compiler to compile for non-Deno environment. And then there's importing from URL: it's useful in a Deno-only project but in a 'hybrid' project you have to duct-tape it together.
All in all: A Deno only project: go for it. A Javascript with multiple targets: it's not ready for that (yet).
No, I don't think it will, but it will get a sizable following. Node.js is a behemoth that will be hard to kick off. The upsides of Deno just aren't that large! No ambiguity in imports and nicer APIs are great, but won't convince a large company to rewrite much of their existing codebase.
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.
I wrote some small scripts in it, I want to love it but in practice it's been quite painful, especially if the project has some browser/Node stuff in it too. My editor (vs code) does not want to understand both at the same time.
I tried to use Deno to execute tests for a ServiceWorker project (on Cloudflare Workers), it makes a lot of sense because Deno is a lot closer to a WebWorker than Node is (in terms of global API), but you run into all sorts of problems.
One glaring one is the Typescript compiler not accepting imports that end in
.ts, which is a total killer for Deno. I need to use the typescript compiler to compile for non-Deno environment. And then there's importing from URL: it's useful in a Deno-only project but in a 'hybrid' project you have to duct-tape it together.All in all: A Deno only project: go for it. A Javascript with multiple targets: it's not ready for that (yet).
Do you believe it could become the main JS runtime in the upcoming years? 👀
No, I don't think it will, but it will get a sizable following. Node.js is a behemoth that will be hard to kick off. The upsides of Deno just aren't that large! No ambiguity in imports and nicer APIs are great, but won't convince a large company to rewrite much of their existing codebase.