Michael Collison (Aug 20 2020 at 19:22): Michael Collison (Aug 20 2020 at 19:22):I'm surprised this topic has not come up (or I missed it). What is the community assessment of Mozilla's decision on the future of wasmtime?
Andrew Brown (Aug 20 2020 at 23:10):I'm trying to give @Till Schneidereit and others time to think through how they want to articulate their strategy going forward; I think in the next week or two we'll probably hear from him.
Till Schneidereit (Aug 21 2020 at 10:19):Thanks for raising this, @Michael Collison, and thanks for looping me in, @Andrew Brown!
We're still working through the implications of the changes at Mozilla, and will indeed have to wait a bit until we can give a full update. In the meantime, I can state with confidence that I see absolutely no concerns about negative long-term impacts on Wasmtime's resourcing, nor the Bytecode Alliance more generally. We'll share more as things get firmed up.
Michael Collison (Sep 14 2020 at 08:10):Is there any update on this topic?
Till Schneidereit (Sep 18 2020 at 13:20):It's still too early to share more information, unfortunately. However, I can by now even more confidently state that resourcing for Wasmtime isn't imperiled by these changes. We'll follow up here with actual information as soon as we can, but it'll be another few weeks before we'll be able to do that, I'm afraid
Till Schneidereit (Oct 28 2020 at 09:31):Hey All, I wanted to follow up here, now that we finally have substantial news out there. As announced in Monday's 1-year update on the Bytecode Alliance, most of the Wasmtime team moved over to Fastly. That's what I was alluding to in expressing confidence about the resourcing, but I wasn't able to talk about it yet. The article includes a few more details about what all this means for our team and for Mozilla, so I highly recommend reading it. And I'm happy to try to answer any additional questions you might have, here or in DMs :smile:
Last updated: Oct 23 2024 at 20:03 UTC