21–30 of 193 posts
Earlier quoted context omitted.
> Plus, bought by Anthropic. Who thinks this is a positive?!
It means they're a whole lot less likely to run out of money, which makes them a safer bet as a dependency.
(still reserving judgement on Bun, though — I mean, we'll soon see, one way or the other!)
> Deno now defaults to npm: This is an interesting development. npm after all is the de-facto ecosystem and leaning into it makes sense. I'm wondering how Deno would've been received if it supported npm and package.json from day 1.
I actually lost interest in Deno once it started leaning into NPM. I thought it was a bold and wise idea to make a clean break from the mess of Node and restart with a sensible ecosystem. Absent that... I'm just sticking with Node.
No way it would go through standard build pipelines, or team skills.
Earlier quoted context omitted.
> Plus, bought by Anthropic. Who thinks this is a positive?!
It means they're a whole lot less likely to run out of money, which makes them a safer bet as a dependency.
I wonder how Deno's faring. Node's the stable solution and will be with us forever. You can now use TypeScript with it and, soon enough, you'll be able to build your app to a single executable -- including native deps. Bun's chaotic but, nonetheless, it's _fast_ and it's taking an interesting approach by including everything in the stdlib. Plus, bought by Anthropic. Deno had an awesome story with the sandbox and ease…
Earlier quoted context omitted.
It means they're a whole lot less likely to run out of money, which makes them a safer bet as a dependency.
> safer bet as a dependency. The recent 1 million line vibe coded PR suggests it is not so reliable as a dependency.
I'm not deep in the webdev / node / Bun ecosystems, I've just been a happy user of Deno for small services for several years. Can someone explain why it sounds like there's such rapid growth of Bun? Is it just being used as a bundler, but not as JS runtime?
Just the permission system alone (though I wish it extended to modules) is so compelling with Deno that I'm perplexed at why someone would transition from node to bun and not node to Deno.
Earlier quoted context omitted.
I actually lost interest in Deno once it started leaning into NPM. I thought it was a bold and wise idea to make a clean break from the mess of Node and restart with a sensible ecosystem. Absent that... I'm just sticking with Node.
As someone that works in projects with standard IT tools, not supporting NPM made it a non starter for us. No way it would go through standard build pipelines, or team skills.
The release post for v2.8 is not yet published. Check GitHub releases page for the latest release status of Deno.
Deno: has a basic permission model that is very helpful, written in Rust, and native TypeScript support. I'm not deep in the webdev / node / Bun ecosystems, I've just been a happy user of Deno for small services for several years. Can someone explain why it sounds like there's such rapid growth of Bun? Is it just being used as a bundler, but not as JS runtime? Just the permission system alone (though I wish it extend…
Earlier quoted context omitted.
> Plus, bought by Anthropic. Who thinks this is a positive?!
It means they're a whole lot less likely to run out of money, which makes them a safer bet as a dependency.