2 ms·
I'm not sure that they meant those specific runtimes would be premium products. My read was that anyone could more easily configure a runtime to expose (or not
by sbarre 6y ago
I'm not sure that they meant those specific runtimes would be premium products.
My read was that anyone could more easily configure a runtime to expose (or not expose) the underlying bindings that it requires, vs. just having them all in there by default.
I think "us" in that statement is the Deno community, not Deno the company.
But maybe I'm wrong.
- not_knuth 6y agoClicking around the website and reading more comments leads me to believe that this is the product they intend to monetize with: https://deno.com/deploy https://deno.com/deploy I still find it strange that there is no mention of it in the post...
- sbarre 6y agoThat makes sense... So if you're up for it, you can still roll your own deployment infrastructure and tailor your builds as needed etc.. and support all of that internally. Or you can pay Deno to handle it for you and you can focus on building your apps.