5 ms·
It’s hard for them to have two projects (the open source Deno and a closed source Deploy runtime that’s not actually Deno). I’m wondering if this was open sour
by inglor 3y ago
It’s hard for them to have two projects (the open source Deno and a closed source Deploy runtime that’s not actually Deno).
I’m wondering if this was open source rather than proprietary this sort of bug allowing a DDoS would have been caught before production. I know of multiple times in the past security issues were detected by the community and dealt in Node before they reached production.
It must be a challenge for the Deno team competing against the likes of Amazon or Google without the andvantage/burden of open source.
- rmorey 3y ago> that’s not actually Deno You're saying Deno Deploy does not run Deno under the hood?
- inglor 3y agoCorrect. It runs a separate runtime.
- rmorey 3y agothank you. is this documented somewhere?
- inglor 3y agoNot that I know, my reference was meetings with people from the Deno team (many of whom are friends) - I'm not sure it's documented but it can easily be verified. Just try to do `Deno.connectDatagram` on deploy for example and see it's missing.
- mmastrac 3y agoI'm working at Deno, mostly on the open-source version so I can clarify a bit. The open-source code of Deno runs in Deploy, but some APIs are disabled and others are adapted for cloud use (ie: Kv works in CLI and Deploy, but is distributed on Deploy). Under the hood Deno Deploy is just Deno with scale built in. It's obviously not a simple soundbite but I recently built the new Deno.serve API implementation and the same code effectively runs in the CLI and Deploy modulo what's necessary to get it working in the Deploy environment.