I deployed my first non-trivial Deno app to production in 2023. There were some teething issues with learning to keep the lock file in sync, especially in a repo with multiple entry points each with separate lock files. Some of the granular permissions stuff didn't work how I expected, to the point where I almost gave up and just allowed network to/from all hosts. But overall the experience was good, and I have positive feelings towards Deno. I look forward to seeing where they take it.
Deno in 2023
11–20 of 235 posts
Re: Deno in 2023
#12Earlier quoted context omitted.
To be fair to the original commenter I believe they were making a Mean Girls (2004) reference. The line in question is "Stop trying to make fetch happen. It's not going to happen.". Likely just a funny quip and nothing serious :)
Yes, and that’s actually the problem with the comment. HN guidelines are for substantive discussions, not funny quips. There’s a few HN comment guidelines [1] that could apply here, but the most directly applicable one is “Omit internet tropes.” [1] https://news.ycombinator.com/newsguidelines.html
It's both a throwaway quip, and a real sentiment: I think that Deno is not getting any traction, surely not the intended traction expected when it was created (and by Node's creator no less), and it will just keep hanging on in the fringe.
Besides, it wouldn't hurt HN to loosen up a little once in a while. You know, obsessive total adherence to rules is never a good thing - even to the law.
Re: Deno in 2023
#13[flagged]
Give them a break, competition is clearly a good thing in this domain. At least drives node.js from stagnation.
Does it though? I see Node developing quite quickly by itself, even though Deno doesn't have any real adoption to give them anything to worry about.
Sure, competition is good. But I've seen a lot of devs get caught into eternally fringe doomed projects.
Which is fine if you understand what it is, but can hurt you if you think you're making a sure bet on a soon-to-be major platform.
Re: Deno in 2023
#14What is the state of Deno's node.js compatibility when compared to Bun?
Deno wasn't originally designed to be node compatible, but I think they realized nobody would want to switch to it because node is so prevalent already...
Re: Deno in 2023
#15[deleted]
Re: Deno in 2023
#16Earlier quoted context omitted.
Yes, and that’s actually the problem with the comment. HN guidelines are for substantive discussions, not funny quips. There’s a few HN comment guidelines [1] that could apply here, but the most directly applicable one is “Omit internet tropes.” [1] https://news.ycombinator.com/newsguidelines.html
It's both a throwaway quip, and a real sentiment: I think that Deno is not getting any traction, surely not the intended traction expected when it was created (and by Node's creator no less), and it will just keep hanging on in the fringe. Besides, it wouldn't hurt HN to loosen up a little once in a while. You know, obsessive total adherence to rules is never a good thing - even to the law.
If the original comment was funny，I wouldn’t have downvoted.
But it’s just low effort, extremely online snark.
Re: Deno in 2023
#17What is the state of Deno's node.js compatibility when compared to Bun?
Deno wasn't originally designed to be node compatible, but I think they realized nobody would want to switch to it because node is so prevalent already...
I think the main appeal of projects like Bun and Deno is the built-in tooling for building/bundling modern typescript applications without requiring dozens of dependencies for even a basic hello world app.
If node.js decided to include functionality similar to what is available on Bun/Deno, both projects would probably lose traction quickly.
Re: Deno in 2023
#18If Deno is looking for more growth they should make it super easy to run Next.js with it
Re: Deno in 2023
#19Earlier quoted context omitted.
Deno wasn't originally designed to be node compatible, but I think they realized nobody would want to switch to it because node is so prevalent already...
I think the main appeal of projects like Bun and Deno is the built-in tooling for building/bundling modern typescript applications without requiring dozens of dependencies for even a basic hello world app. If node.js decided to include functionality similar to what is available on Bun/Deno, both projects would probably lose traction quickly.
Not sure what modern typescript means, but you only need one or two dependendencies (esbuild and tsc) unless you are doing something more involved, in which case deno alone might not work either.
Re: Deno in 2023
#20You can join the waitlist in the sneak peak of JSR linked in the end of the article: https://jsr.io/waitlist I'm curious on what the Deno team is building here.
JSR = JavaScript Registry (from the site). It seems fairly clear this is a package registry, i.e. an NPM alternative.