An annual summary of WAMR's progress in 2024 #121
Conversation
|
What's the status of that? Is it ready to merge or is there any feedback to address before that @pchickey ? |
|
There are no blockers from me, my feedback was addressed. |
|
Thanks @pchickey , what are the next steps? Do we need to chase anybody else to review the PR? |
|
The TSC reviews blog posts before publication, and I've pinged them to get attention on this. |
|
Thanks, @pchickey -- I've added this to the TSC agenda for our next meeting this coming Tuesday, and know folks are already aware of the PR and reviewing. Stay tuned. |
|
|
||
| ### Shared Heap: Efficient Memory Sharing | ||
|
|
||
| Another significant feature introduced in 2024 is the shared heap. This feature addresses the challenge of sharing memory between the host and Wasm. Traditionally, copying data at the host-Wasm border was inefficient, and existing solutions like externref lacked flexibility and toolchain support. |
There was a problem hiding this comment.
Will you mention that this feature is experimental and clarify that the intent is to work towards a standardized approach within the CG? This would help set expectations for early adopters and ensure alignment with the broader Wasm ecosystem. Looking forward to further discussions on this!
There was a problem hiding this comment.
Sure. I will update the PR soon.
@loganek @yamt @no1wudi
We've written an annual summary to recap the achievements of the WAMR community in 2024. Please review it and share your feedback. I've left it in draft form to gather comments until next Monday. Thank you all.