2 ms·
I feel its odd for a compiler/language toolchain to have a cloud offering. I understand the motivations but 20% of the article was about their Deno Deploy produ
by pests 3y ago
I feel its odd for a compiler/language toolchain to have a cloud offering. I understand the motivations but 20% of the article was about their Deno Deploy product and how to calculate API costs...
I understand its only when using their cloud and there is a local implementation, but I just couldn't imagine using a feature in LLVM, for example, where if you were to upload the binary to a specific cloud it would use a different implmentation that costs behind the scenes.
It just feels odd to me. I guess it's kind of cool. Maybe different clouds can implement the underlying KV and then this becomes cross-cloud with different underlying benefits without changing the code. But I'm not entirely sure how I feel about this.
- wmf 3y agoThese features pay for Deno. If they don't exist, Deno doesn't exist.
- pests 3y agoI agree projects need funding and developers need to be paid... Deno was released 4 years before Deno Deploy and existed just fine.
- billywhizz 3y agothere is also a b2b game in play here by deno. i'd imagine a FaaS JS/TS only platform powered by Deno runtime is attractive to a lot of already existing web services who want to expose the ability to write webhooks/event-based functions in their service offerings? https://deno.com/blog/netlify-edge-functions-on-deno-deploy https://deno.com/blog/netlify-edge-functions-on-deno-deploy