3 ms·

Is there something about Deno that makes Edge functions good to be based on it - Netlify also has its Edge functions in Deno https://docs.netlify.com/edge-funct

Is there something about Deno that makes Edge functions good to be based on it - Netlify also has its Edge functions in Deno https://docs.netlify.com/edge-functions/overview/ https://docs.netlify.com/edge-functions/overview/ maybe just coincidence, but seen two edge functions in Deno implementations in the last hour so makes me wonder.

inian 4y ago
One reason is that Deno can run on v8 isolates which start up really quickly. This makes the deploys near instantaneous and helps with cold start time too. The DX with Deno is pretty neat since it comes in bundled with a test runner, doc generator, linter, bundler, etc.
joshxyz 4y ago
Honestly Deno is a pain in the ass to work with which is what put us off from continuing to use Supabase. The developer tooling is just not mature yet, and buggy in lots of ways. Edge technologies are nice until they get into your way of work.
- inian 4y ago
  Can you share some examples where the tooling fell short?
  - joshxyz 4y ago
    https://github.com/orgs/supabase/discussions/8779 https://github.com/orgs/supabase/discussions/8779 That one lol. Are there any solid reasons to not support other runtimes? Appwrite for example supports Nodejs.
    - lytedev 4y ago
      This looks like you're complaining that your development environment is not configured to work with Deno and is instead configured to process typescript files for a completely different runtime? Deno's tooling is top notch. The fact that most developers' systems are all setup for Node or some Node-based compilation step is hardly the fault of Deno. Editors in general are still figuring how to have and manage configuration that is flexible enough for different language servers, linters, formatters, test runner, debuggers, etc. It's not really fair to either Deno or even your editor, though your editor is clearly more "at fault" in this scenario.
    - inian 4y ago
      Added a comment in the discussion [1] with a video and a quickstart guide on how you can configure VSCode to work with Deno. Let's continue the discussion there in case those steps don't work for you. With respect to supporting other runtimes, it mostly comes down to focussing on providing a great experience with one runtime first. And based on your feedback, we still have some work to do there. [1] https://github.com/orgs/supabase/discussions/8779#discussioncomment-5587610 https://github.com/orgs/supabase/discussions/8779#discussion...

inian 4y ago

One reason is that Deno can run on v8 isolates which start up really quickly. This makes the deploys near instantaneous and helps with cold start time too. The DX with Deno is pretty neat since it comes in bundled with a test runner, doc generator, linter, bundler, etc.

joshxyz 4y ago

Honestly Deno is a pain in the ass to work with which is what put us off from continuing to use Supabase. The developer tooling is just not mature yet, and buggy in lots of ways. Edge technologies are nice until they get into your way of work.

inian 4y ago
Can you share some examples where the tooling fell short?
- joshxyz 4y ago
  https://github.com/orgs/supabase/discussions/8779 https://github.com/orgs/supabase/discussions/8779 That one lol. Are there any solid reasons to not support other runtimes? Appwrite for example supports Nodejs.
  - lytedev 4y ago
    This looks like you're complaining that your development environment is not configured to work with Deno and is instead configured to process typescript files for a completely different runtime? Deno's tooling is top notch. The fact that most developers' systems are all setup for Node or some Node-based compilation step is hardly the fault of Deno. Editors in general are still figuring how to have and manage configuration that is flexible enough for different language servers, linters, formatters, test runner, debuggers, etc. It's not really fair to either Deno or even your editor, though your editor is clearly more "at fault" in this scenario.
  - inian 4y ago
    Added a comment in the discussion [1] with a video and a quickstart guide on how you can configure VSCode to work with Deno. Let's continue the discussion there in case those steps don't work for you. With respect to supporting other runtimes, it mostly comes down to focussing on providing a great experience with one runtime first. And based on your feedback, we still have some work to do there. [1] https://github.com/orgs/supabase/discussions/8779#discussioncomment-5587610 https://github.com/orgs/supabase/discussions/8779#discussion...