We (fly.io) use Deno pretty intensely. We really like:
* No npm spaghetti, just requiring a URL is a win
* It'll build a lightweight static binary. Usually way smaller than the equivalent node Docker image
* The stdlib and every community lib were written at a time when async/await was the norm. So they're all very nice to use compared to wildly inconsistent node libs
Very interesting to hear. I didn't realize Deno was "production ready", I'd been curious about it for a long time.
Your comment inspired me to study Deno deeper and consider it for practical use. In addition to the pros you've listed, seamless integration of TypeScript sounds fantastic.
Would love to hear more about how Deno is used in your company!
* No npm spaghetti, just requiring a URL is a win
* It'll build a lightweight static binary. Usually way smaller than the equivalent node Docker image
* The stdlib and every community lib were written at a time when async/await was the norm. So they're all very nice to use compared to wildly inconsistent node libs