Vercel should fork and maintain Deno
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")
Thoughts on the future of deno post Cloudflare?
(
14 comments
| 2 points
| on HN
)
Vercel will place in platform specific features or that work only on Vercel.
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.
You can build a server with a local database with zero external dependencies, it has JSX and SQLite built in.
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.
They were great at standards too; if it wasn't in the Deno namespace it was standardised. Import maps and Temporal early were cool and i Learned a lot reading release blogbosts that linked to tc39 proposals.
It had some achilles heels with vite & meta frameworks and the linter wasn't great (there was a draft PR to use oxlint which would fix that) but I'm sad to see it die over the last year, the writing was well and truly on the wall before officially closing.
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???
Big if, but if they set up a foundation and it has enough steam to keep improving it could be a renaissance for Deno being no longer connected to a company that needs to focus on being a temu Vercel so it can be a stable, secure runtime that attract engineers that like typescript but don't want the node/npm quagmire that were, quite reasonably and rightfully in hindsight, turned off by Deno company.
Stable funding + a 3.0 with; oxlint and some rough edges with vite and LSP integration and I would be convinced to go back. (@std being bundled would be amazing too)