4 ms·
I tried Deno out extensively last year and found it wasn't really ready for production yet. There's a lof of packages missing to be able to address common use c
by whatatita 4y ago
I tried Deno out extensively last year and found it wasn't really ready for production yet. There's a lof of packages missing to be able to address common use cases, and the node -> deno converters were really hit or miss.
Have you had a good experience with it?
- beeandapenguin 4y agoThe question didn’t ask about production readiness. But I would say that it depends on your use case. For example, I think Deno is an excellent alternative to Node for general purpose scripting, but that doesn’t require production readiness. On the other hand, platforms like Slack[1] and Netlify[2] are betting on Deno for their next generation developer platforms. These platforms are still considered beta, but I think that’s a decent indicator to track status of production readiness. - [1]: https://api.slack.com/future https://api.slack.com/future - [2]: https://www.netlify.com/blog/announcing-serverless-compute-with-edge-functions/ https://www.netlify.com/blog/announcing-serverless-compute-w...