hey Andy from Deno here. thanks for your comment. we reduced our Deno Deploy regions not because Deno is in decline. (in fact we have seen about 2x adoption since release of Deno 2.) it's just that we noticed more users using Deno Deploy for hosting applications vs. edge functions, which was our original vision for Deploy. in many scenarios, application performance is improved with fewer, more highly trafficked regions vs. many spread out but more idle regions. we will be covering that in more detail in a dedicated blog post next week.
Wow! Didn't expect anyone from Deno team to respond. I just thought I was shouting stuff in the void for my fellow HN people at most reading it.
Thanks for the clarification.
I have some questions though:-
Aside from the fact that deno allows npm compatibility, how is deno deploy any better than cloudflare hosting which I currently use, since cloudflare workers also have some compatibility layer I suppose and cloudflare workers can and do host applications and edge functions both.
I can understand if things like nextjs which don't run as smoothly on cf workers, if at all (I haven't tried them but I do know that its easier to run nextjs on vercel than any other competitor), but nextjs can run easily on deno, so that might be a really big niche tbh
But as a sveltekit user, here's my opinion
I have deployed so many sveltekit websites to cloudflare workers, 100k limit never disappoints me or limits me, cf workers also has a kv which is good for simple databases. I am seriously considering to always use cloudflare workers since currently I am just a student and it gives me 100k requests per month limit and after that its still really really cheap.
I had compared deno's tier and cf tier's sometime ago and cf was the winner there, I don't know what's the situation now but I am willing to hear.
Cf workers wrangler developer-experience is genuinely decent in my opinion, not as easy as deno deploy I suppose but still its worth it given all the previous points.
Deno is really nice compared to node, I in fact was the guy who watched fireship video and then the deno video itself and then I legit went to my brother's room knocking on his door (my brother is also a coder, in fact he knows his stuff whereas I am just this 16 year old student) and I legit wanted him to try out deno. But I am having mixed opinions now and I don't mean any defamation of deno team who are really nice and kind for what I've seen.
Have a really nice day Andy. Hope deno achieves success.
hey HN, i'm Andy, part of the Deno team. we're really excited to get a release candidate out there for what will soon become 2. it's been a long road to get here and we're really just beginning. happy to answer any questions!
Hi Andy! Deno basically restored my hope in being able to understand (T|J)S tooling, thanks for working on this amazing project.
2 questions:
Support for TS in notebooks in VSCode(ium) is currently broken; are there plans for resolving issues with definitions used across different cells?
Future plans for bundler sound interesting - is it something potentially able to replace e.g. esbuild for bundling frontend applications? I'm specifically curious because that would imply (static) Deno's import resolution for browser-run apps - one can use @luca's esbuild plugin, which is nice, but interacts poorly with other, custom plugins and has some rough edges.
hey gang, andy from deno here. we're really excited about the possibilities of this API, especially around building real time applications or pushing UI changes to the client without a page reload.
we're looking for feedback and happy to answer any questions!
hey hn, andy from deno here. from working with larger companies interested in using our v8 isolate cloud infrastructure, its no surprise that terraform is a preferred approach for reliably provisioning and managing many projects on Deno Deploy/Subhosting at scale.
we know our documentation is a bit sparse (we're working on it!), but we've included a walkthrough on how to deploy local code/assets to Deno Deploy via Terraform. we'd love to get any feedback. is this something you'd use?
pulling from an API / scraping data, sending emails/notifications/reports, backing up databases/snapshots, checking availability of various services, pinging website, pre-warm up apps/scale applications, various maintenance tasks.
Why on earth would you copy Cron's incomprehensible syntax? You're writing code in a statically typed language! You can make a nice type checked API that actually is understandable without having to use one of the many many crontab generator UIs.
Crazy API design!
Edit: seems like there is a WIP typed API but I still have no idea why you would lead with the terrible one...
Yes, we're anticipating more spiky workloads because of this. Deno Deploy is already designed to handle spikes, but we also have a few additional mitigations in place for Cron. For example, we will limit concurrent dispatches for the same project/user/organization, which may slightly delay the execution of specific cron tasks.
Or add a default randomness factor that makes it run within a certain time (like 60s or 5m) of the target, perhaps with an additional charge to run at the exact time if people have that requirement.
Personally I would stay within your niche and focus on documentation, guides, and outreach to convert more people to your stack. A few simple but very reliable easy solutions is better than a lot of not great solutions.
