Deno in 2023
deno.com
Deno in 2023
1–10 of 235 posts
Re: Deno in 2023
#2[flagged]
Re: Deno in 2023
#3Deno Deploy dropped from 35 GCP regions to just 12: https://news.ycombinator.com/item?id=39127598
Re: Deno in 2023
#4I'm really interested in deno, but I didn't yet have the chance to test it properly.
I would love for this year to see the runtime support for either Google Cloud Functions or AWS Lambdas
Re: Deno in 2023
#5[flagged]
This is a low effort comment, overly negative and provides no value to the discussion.
Re: Deno in 2023
#6You 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.
Re: Deno in 2023
#7What is the state of Deno's node.js compatibility when compared to Bun?
Re: Deno in 2023
#8[flagged]
Give them a break, competition is clearly a good thing in this domain. At least drives node.js from stagnation.
Re: Deno in 2023
#9[flagged]
This is a low effort comment, overly negative and provides no value to the discussion.
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 :)
Re: Deno in 2023
#10Earlier quoted context omitted.
This is a low effort comment, overly negative and provides no value to the discussion.
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.”