<ocdtrekkie>
Awesome, your reputation for open sourcing nearly all your stuff will be unblemished again!
<xet7>
kentonv: How it is different from Miniflare?
<xet7>
And would it be possible to run newest Node.js 18 at Sandstorm?
<xet7>
Currently WeKan is Node 14
<xet7>
Does some of this Workers/Node/Deno work solve problems with amount of Javascript code and amount of data? For example, WeKan has some large dependencies, like exceljs, mermaidjs, etc. And, sometimes WeKan is importing a lot of cards from Trello etc. Could it all run at CloudFlare workers etc?
<ocdtrekkie>
Meteor 2.7.2 should fix why Sandstorm couldn't upgrade Meteor
<xet7>
How compatible this Workers/Node/Deno framework would be with others like AWS/Azure/Google serverless?
<ocdtrekkie>
kentonv: When you have the code ready to share, do you think you could take like the chat demo from the Workers launch and put it in an SPK as a demo?
<kentonv>
xet7, Miniflare is a simulator, re-implementing the APIs on top of Node. What we're going to release will be the actual API implementations that power Workers in production.
<kentonv>
One thing that might be interesting for Sandstorm would be building the Workers runtime directly into Sandstorm, rather than having apps package up their own copies. This would make grains much more efficient -- faster startup, less memory usage. And the Workers Runtime conveniently cares deeply about never breaking backwards compatibility.
<kentonv>
ocdtrekkie, interesting question. Most of the chat demo code is really about supporting multiple chat rooms via durable objects. In Sandstorm you'd want one room per grain. I haven't thought a lot about how to make code like that translate over nicely.
<Corbin>
kentonv: Please don't take this as a feature request, but more as a sign of what folks might want to build on top: Will the Workers source dump come with Kubernetes or other cloud API support, or do Workers have to be booted on bare metal?
xet7 has quit [Quit: Leaving]
<kentonv>
Corbin, roughly speaking, we'll release something that operates like Node. You'll be able to put it into whatever container runtime you want, but it'll probably be up to the community to build any complex integrations with things like Kubernetes.
<Corbin>
kentonv: That makes sense. Thanks for your effort on this; I'm sure that there's piles of behind-the-scenes labor.