There are plenty of moribund open source projects. But looking at this month's 2.3 release, Deno's future strikes me as the opposite of bleak.
As for Deno Deploy, sure —¹ it may fail. But regarding the Deno folks scaling their footprint in response to changes like real-world usage patterns, adoption timelines, our rapidly-contracting economy, or whatever, that's a far better response than ostriching in the longer run.
¹ This em-dash was lovingly hand-crafted by a Mac user. Please don't em-shame.
I meant deno's future as of how the company would survive with competitors/ the ecosystem growing and node adopting. Because the company is basically the only one "really" working on the product, if the company can't find a decent source of revenue, (I am not sure "what" is the product that deno sells that others can't / aren't selling already ie. bunny cdn / supabase hosting deno subhosting)
I would love deno to win, maybe be even faster than bun and maybe help with permissions a little bit more as I played around with deno scripts and it quickly devolved into a permission nightmare from my personal experience, maybe I am inexperienced, but I didn't had the issues in bun.
Same, my typographically-savvy friend. This "dead giveaway" too shall pass — first it was certain words, today it's em-dashes, and tomorrow we'll be forced to introduce grammatical errors.
There are plenty of moribund open source projects. But looking at this month's 2.3 release, Deno's future strikes me as the opposite of bleak.
As for Deno Deploy, sure —¹ it may fail. But regarding the Deno folks scaling their footprint in response to changes like real-world usage patterns, adoption timelines, our rapidly-contracting economy, or whatever, that's a far better response than ostriching in the longer run.
¹ This em-dash was lovingly hand-crafted by a Mac user. Please don't em-shame.