41–50 of 235 posts
Why did he feel the need to build a competitor to his own product? Whatever features are supposed to make Deno "better" than Node...why didn't he just work on integrating them into Node?
I understand that sometimes changes to software can be infeasible, especially if they are large fundamental/foundational changes, but this is still a bit of a head scratcher to me.
With Slint [1] we're working on a framework which allow to make a desktop GUI in Javascript/Typescript, without bringing a browser/webview. Currently, we do it by using binaries through napi-rs so we can bring in a window using the platform native API. And then we do some hack to merge the event loops.
But if Deno supports bringing up a window directly, this means we can just ship wasm instead of native binary for all platform. And also I hope event loop integration will be simplified.
Although we'd also need more API than just showing a window (mouse and keyboard input, accessibility, popup window, system tray, ...)
Edit: I got excited a bit too early. The WebGPU feature doesn't include the API to launch a Window. One still need to rely on an extra library binary.
I know it sound silly but I love the aesthetic behind Deno's brand, it makes me want to use it for one project or another. Node.js is so old now. it's reliable but boring. I want something new, bold, and daring. Node.js is not it, although it was ~11 years ago. It's interesting how our views change.
So the old-timers remind us, "Choose boring technology." Reliable and boring is a good thing.
On the other hand, I recently started learning Bun, and oh what a breath of fresh air, it makes things fun again. I love that its codebase is so readable and small still, and everything is freshly designed with the insights of experience and hindsight. It doesn't have the accumulated cruft, years of decisions and compromises.
So, sometimes it's great to shed the old and grow with the new generation.
Earlier quoted context omitted.
sure but is that a bad thing? this regions probably see next to or zero use and cutting them frees up money to be used on other things.
They’re operating like a startup, which like you say should be perfectly fine. Can’t pretend like a giant when you don’t have the bank account for that. Though they’re also selling a developer ecosystem. A lock-in. Are you willing to bet your company’s own software tools on a vendor that could go bankrupt from their other (hosting) business? The question is if Deno hosting dies, will Deno as a platform still thrive?
that I am unsure about, a large part of the appeal at least for me is the deno deploy.
URL imports are a bit of a hassle when you are trying to get them from say a private github repo.
Earlier quoted context omitted.
> If node.js decided to include functionality similar to what is available on Bun/Deno, both projects would probably lose traction quickly. I believe this too. The big appeal for me is not having to install typescript, eslint, jest AND then set up all the configs. deno has nice defaults, though the importing via URLS and browser compatible API do make deno very tempting
that feels like a really weak value prop to me. how often do you have to install that stuff? how hard is it actually? can you really not use, e.g. for react, the typical vite starter and it's done?
Interestingly, Deno and Node were both originally developed by the same person, Ryan Dahl. Why did he feel the need to build a competitor to his own product? Whatever features are supposed to make Deno "better" than Node...why didn't he just work on integrating them into Node? I understand that sometimes changes to software can be infeasible, especially if they are large fundamental/foundational changes, but this is…
You can do this using containerization technology, no need to invent this per language runtime.
Interestingly, Deno and Node were both originally developed by the same person, Ryan Dahl. Why did he feel the need to build a competitor to his own product? Whatever features are supposed to make Deno "better" than Node...why didn't he just work on integrating them into Node? I understand that sometimes changes to software can be infeasible, especially if they are large fundamental/foundational changes, but this is…
> A program run with Deno has no file, network, or environment access unless explicitly enabled. You can do this using containerization technology, no need to invent this per language runtime.
> A program run with Deno has no file, network, or environment access unless explicitly enabled. You can do this using containerization technology, no need to invent this per language runtime.