← Back to context Comment by pier25 10 hours ago > So Cloudflare killed DenoUh no. The lack of users killed Deno. 3 comments pier25 Reply hoppp 9 hours ago Platforms like supabase or netlify use deno for serverless functions, so they should have been supporting it more. pier25 8 hours ago Aren't Supabase or Netlify customers of Deno Deploy? hoppp 2 hours ago I don't think so, I think they just used deno as a runtime with their own cloud.One of them should fork if it's cheaper than migrating because a lot of Deno code is not portable.
hoppp 9 hours ago Platforms like supabase or netlify use deno for serverless functions, so they should have been supporting it more. pier25 8 hours ago Aren't Supabase or Netlify customers of Deno Deploy? hoppp 2 hours ago I don't think so, I think they just used deno as a runtime with their own cloud.One of them should fork if it's cheaper than migrating because a lot of Deno code is not portable.
pier25 8 hours ago Aren't Supabase or Netlify customers of Deno Deploy? hoppp 2 hours ago I don't think so, I think they just used deno as a runtime with their own cloud.One of them should fork if it's cheaper than migrating because a lot of Deno code is not portable.
hoppp 2 hours ago I don't think so, I think they just used deno as a runtime with their own cloud.One of them should fork if it's cheaper than migrating because a lot of Deno code is not portable.
Platforms like supabase or netlify use deno for serverless functions, so they should have been supporting it more.
Aren't Supabase or Netlify customers of Deno Deploy?
I don't think so, I think they just used deno as a runtime with their own cloud.
One of them should fork if it's cheaper than migrating because a lot of Deno code is not portable.