It's as bad as Deno Deploy has always been (used by Netlify edge functions, Supabase, and others).
To me CF Workers are more about interacting with the CF CDN, doing lightweight HTTP stuff, etc. I would never use Workers to build a full server application. Their custom runtime locks you in, it's extremely barebones, and obviously almost no NPM modules are compatible.
They are working on Node compat which will probably help but I feel CF hasn't been investing enough into their cloud products (Workers, Pages, etc). DX is still hit and miss and progress overall feels glacial.
My superficial impression is they've been investing more in their networking services for enterprise customers but don't take my word for it. I don't pay much attention to their announcement weeks.
Any thoughts on implementing really "enterprise" languages like Java or C# so you could attract "the big boys" (corporations)?
I know the corporations I work at are very anti-node.js and very pro-C# and everything needs to be approved by a tech committee. I don't think we could get Supabase approved (and instead we fork millions a month to Azure instead).
Just a bit of feedback. I'm not a fan of C# or Java at all these days given how good Rust, node.js/Typescript/Deno have become. I just now work for 40,000+ person companies where I know this would be a non-starter unless you were super lucky to get all approvals aligned and be on one of the "cool" team.
Maybe not the pivot/user feedback that aligns with your goals. :D
We won't add support for other languages in our Edge Functions (beyond WASM support), but we are adding native support for other languages in our client libraries. For example, we already have C# support: https://supabase.com/docs/reference/csharp/introduction
The idea is that you'd just use the client libraries in your favourite framework.
We are planning to focus on the Deno and WASM ecosystem. If C# complies to WASM, we would be able to run it, but have a lot of work to do to make this seamless.
