Given the news of Deno being acquired by Cloudflare and its already stated eventual sunset, someone has to take over deno.
Vercel certainly has the resources, I am looking for a job and would love to work on Vercel's deno maintenance (which I suggest should be renamed to "veno", or "vino")
It took nearly $30 million in VC to fund Deno's existence and it got dropped like a rock by Cloudflare so there's probably nothing financially-attractive about the software and no hope of self-sustainability.
Vercel taking it over would be a bandaid solution, back to square one as soon as they want to cut expenses or a PE firm makes an offer their investors can't refuse. It probably wouldn't survive this decade there.
The Apache Foundation is good for projects like this.
I used it for a while, it was a sane TypeScript. Most pieces came out of the box. Deno had its own formatter, test runner, standard library, server, could run TS without a transpilation step, KV DB, and god knows what else.
Switching between Deno and standard Node/TS had me thinking why can't all of Node be this nice. Over time Node adopted some of these ideas.
Deno also made some interesting choices around dependency management, its first iteration being literal links in the import statement. This bit and subsequent npm compatibility is guaranteed flamewar material.
I liked it when it first came out and was a substantial DX improvement over node. Unfortunate then that it got undercut by Bun, which had a very similar 'faster, less legacy, and batteries included' value prop. That split the just-not-node audience, and ended up ensuring that neither one ever really got the scale needed to survive independently...
Vercel taking it over would be a bandaid solution, back to square one as soon as they want to cut expenses or a PE firm makes an offer their investors can't refuse. It probably wouldn't survive this decade there.
The Apache Foundation is good for projects like this.
What is the use case, allure, etc.?
I’d prefer to get your thoughts than ask GPT, since you seem to have experience with it.
Switching between Deno and standard Node/TS had me thinking why can't all of Node be this nice. Over time Node adopted some of these ideas.
Deno also made some interesting choices around dependency management, its first iteration being literal links in the import statement. This bit and subsequent npm compatibility is guaranteed flamewar material.
You can build a server with a local database with zero external dependencies, it has JSX and SQLite built in.
Vercel will place in platform specific features or that work only on Vercel.
It makes no sense for Vercel.
The funny part is I didn't even know Deno existed until I saw this post. Then I did some research on it.
If builders don't even know you exist what is the point???